Re: Enterprise A&A, move to CC list
| From: | Pierre-Alain Joye | Date: | Thu, 16 Jan 2003 00:34:29 +0000 |
| Subject: | Re: Enterprise A&A, move to CC list | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-12520@lists.php.net to get a copy of this message | ||
On Thu, 16 Jan 2003 01:24:06 +0100
"Klaus Guenther" <klaus@capitalfocus.org> wrote:
> One downside to LiveUser is that though there are premade containers,
> they don't meet all of everyone's needs, and I don't feel like sitting
> down and writing a new container for every project. I'd probably end
> up writing the whole authentification system from scratch so that I
> would have complete control.
Sadly, this is the case for most of us.
> However, A&A offers single-sign-on for
> multiple applications that don't necessarily need to share a DB or
> even have a DB server accessible via web. If I understand correctly,
> the idea is that you set up a central authentification server
> somewhere on the net and applications can be scattered everywhere,
> like MS Passport... which would exactly suit my need.
Same here, and really soon, within the next months I have to get a beta
or near stable module, includig bridges to the libertyalliance and some
commerce systems. Here I go:)
> With LiveUser, that would basically require a completely new auth
> Container, and since I'll have to write my own perm container anyway,
> I would end up writing nearly everything... :-/
Except if someone write it. That will certainly happen. But the problem
here is not the Auth, this is the remote authentification system itself,
try to look around different RFC or current papers about that and you
will see what I mean :)
pierre