Jan Pieper wrote:
Yeah it would be quite useful.
It would be interesting to see how the system could help with the
following scenario.
The "application" has a users table with an id column. Every user,
regardless of auth method, needs to have a user_id.
Say I authenticate myself via OpenID, I still need a user_id in the
application.
Perhaps the Zend_Auth_Chain object could have a structure for ensuring
a local user row (and thus a user_id) is created when a user
authenticates?
I'd suggest a table structure something like:
Users: id | whatever else
User_Auth: id | mech | detail
Users.id is auto-incrementing, and for every user that exists, there
is one or more User_Auth rows (remember that it should be possible for
the same user to authenticate via more than one system).
The "mech" could default to the class name of the actual authadapter
used, and the "detail" would be e.g. a URI in the case of open id or
ldap etc.
If the chain loader can automate the population of these tables then
that would make it work very nicely IMO.
Col
I hope I understood your mail but I don't think this should be function
of this chain adapter implementation. Your case is very specific.
Hmm that backfired then as I was actually trying to keep it fairly generic.
If you read the OpenId website, you'll see that the first link[1] on the
developers page[2] pretty much describes this structure. This is why I
thought it would be sensible to include this functionality into the
chained auth system.
Col
1. http://www.plaxo.com/api/openid_recipe
2. http://openid.net/developers/
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
