Hey,

I am developing a single sign on system for the EU.
its pretty big, and was wondering if i can ask you some silly
questions:
Here is my topology:

1. 20 x web applications. .net and java
2. 2 x AD LDAP servers. AD is just a bit of LDAP and DNS mixed
together after all.
3. A SSO server i programmed in C#. It acts as a broker and provides
some encapsulation.
i have intended to use it for managing SSO and even federated SSO, but
then after i started playing with XMPP and especially ejabberd, i
realised how powerful xmpp is and how it can do alot of the grunt work
myself and i can use my SSO serevr for custom logic. Like a base
through maybe.

We want to allow SSO within our domain, and then allow controled Fed
SSO over XMPP later.

So:

1. Can i simple just let ejabberd do sso for me ??. i assume it hands
back a session after authentication (with LDAP) completes. i assume i
can just ask ejabberd "is this user "[EMAIL PROTECTED]" logged on anywhere
and where?.
Then if they are i can assume they are already authenticated and then
give a session out to the web apps that corresponds to the same
session from the ejabberd session ID.
Or maybe i just hold a mapping between the XMPP session ID and the
sessionID handled out the the web applications.

As you can see i am a bit confused how to use the xmpp stack. i can
see why i should use but still getting my head around exactly how to
best use it.

ged



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"google-talk-open" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-talk-open?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to