Re: Re: Singe Sign On

From: Date: Sat, 25 Dec 2004 12:29:27 +0000
Subject: Re: Re: Singe Sign On
References: 1 2  Groups: php.pear.general 
Request: Send a blank email to pear-general+get-16463@lists.php.net to get a copy of this message
Alan Knowles wrote:
I've had mild success with pubcookie [google for it], the signup stuff is simple and works ok, however we still havent figured a clean signup strategy for it..
What do you mean by clean signup strategy?
I've done other research on this for another project, it ended up using hidden iframes, header(location:) redirects, cookies and a few md5 checksums to do a similar thing. (unfortunatly I dont own the code or spec document from that now, but the concept is pretty simple)
I'm not sure about this, doesn't sound like a good idea. I want to keep things simple for any programmer trying to authenticate using SSO on any member site. I want it to be as simple as an include file, then a couple of function calls that does everything.
sxip is probably the best option if you dont want to manage a userbase/authentication server.
I want to manage my own userbase, I checked sxip, seems like the 'SSO server' which they refer to as 'Homesite' is written in Java, that shouldn't be a problem if it doesn't need any customization, I will simply deploy the server and then get the SDK( or MDK ) for PHP. Another question is what about user profiles? for example let's assume we want to create a dating service. ( dating.example.com) Profiles for such sites are huge, ( height, eyes, ...etc ) so I suppose I need to store the profiles on the dating service database. so, SSO will only store usernames/passwords But the problem is that what if two services are storing the NAME. then I don;t want to have redundant copies of that... oh, things are getting complex :D Thanks Alan, Ammar
Regards Alan Ammar Ibrahim wrote:
I want to build an SSO for some company. I would like to know if anyone has some ideas where to start? I know that LiveUser might include an SSO thing in the future, but I really don't wanna go for that. Here are some ideas: 1- It must integrate easily with other applications, preferebly without any modifications. e.g. If i decide to install a web mail system, I want it to authenticate against my SSO. 2- Can LDAP help here? 3- I'd like to put SSO on a seperate server, so maybe XML communication might sound like a good idea, XML-RPC anyone? 4- This is a high traffic site, performance is a critical issue. I would appreciate any ideas here. Ammar Ibrahim


« previous php.pear.general (#16463) next »