Wrt SourceID Kit

Nikos Michailidis <[email protected]> Thu, 19 May 2005 17:36:19 +0300
Newsgroups gmane.comp.sourceid.sso.devel
Message-ID <[email protected]>
Dear sso-dev,

I'm a new member in our mailing list and I would like to ask you something 
regarding the SourceID system
architecture, in relation to the system architecture in my application.

The application that I'm currently involved is an EU R&D project demo, (the 
name of the project is MAGNET).

It seems that the current demo implementation on top of the JBOSS server 
can be the starting point for our implementation as well.

However, it is not yet clear to me whether the jboss module can be used as 
it is or there are specific limitations related to the Sourceid demo.
- For example, can I write our own servlets on top of the jboss server and 
invoke them via a browser in the same way we invoke the single sign-on demo?
- How is the local directory space mapped to the URL address space?

I'm currently digging into the code to get a better picture of how it is 
structured and any feedback in this respect would help us reach the
answers more quickly.


Thank you in advance for your time,


Best Regards

Nick Michailidis

___________________________

Nikolaos Michailidis MIEE
TELETEL SA, New Technologies & Applications Group
124, Kifissias Ave., 11526 Athens, Greece
Tel: +30 210 6983393, Fax: +30 210 6983391
[email protected], www.teletel.gr 





---------------------------------------------------------


The information in this e-Mail is confidential and intended solely for the person to whom it is addressed. If this message is not addressed to you, please be aware that you have no authorisation to read the rest of this e-Mail, to copy it, re-transmit it, use it or to furnish it to any person. Should you have received this e-mail by mistake, please bring this to the attention of the sender, after which you are kindly requested to destroy the original message. TELETEL S.A. cannot be held responsible or liable in any way whatsoever for and/or in connection with any consequences and/or damage, resulting from the proper and complete dispatch and receipt of the content of this e-Mail.