After thinking through it a bit more why not do the login work in the Use class? It already does the registratrion work. Seems like the logical place to me. Perhaps the how the User implements the auth is by using an auth class and its derivatives.
Ahoy, Jason ----- "Jason Reusch" wrote: | | I brought this up in IRC the other day (as ahoy_matey) and there seemed to be some interest. I'm interested in creating an internal install and want the users to register and login by authenticating the username/password against an LDAP server. | | Here's my idea for a lazy implementation based on a little poking around. Branch the user register function on some config value then do the check for a valid username against LDAP. The password work occurs in common_check_user, again branch to the appropriate password auth mechanism based on some config setting and do the work there. | | In the chat Evan talked about creating an abstract login class then various auth mechanisms could extent that class (the not lazy implementation), | | I am a newbie here, so any suggestions on how to proceed are appreciated. | | Ahoy, | Jason | | _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev |
_______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
