Login system

Registered by CoD

The DOMuS 2.x login system must be ported in 3.0 asap.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Essential
Drafter:
None
Direction:
Approved
Assignee:
CoD
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
CoD
Completed by
CoD

Sprints

Whiteboard

The domus 2 login system was designed to be simple and effective only wiht mysql databases. Domus 3 supports ldap, ldap+mysql, mysql and many other technologies so we must develop a common unified system to log in and out an user, regardelss of the technology used and of the methods that the wrapper component will use to actually validate the user.

login.php will call a core method login() which will cycle through all authentication systems available
auth systems are definded as a wrapper component AND a specific profile
wrapper login method will return false or true
on false the core login method will move on the next auth system if available or give an error to the user if no system accepted this login
on true the core login will call the load method of the selected auth system and store resulting information in the currentuser component (method storedata)
currentuser::storedata will store user data with an special unique id made by auth system id + user id provided by the auth system (which can be an integer, a string, an ldap uid, whatever the auth system needs to get back to the user data if needed)

(?)

Work Items

Work items:
Basic login routine: DONE
Basic methods to manage users: DONE
Administrator front-end: TODO

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.