Difference between revisions of "Infrastructure Team/Central Login"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
* For now https://obs.sugarlabs.org requires Basic HTTP Auth. | * For now https://obs.sugarlabs.org requires Basic HTTP Auth. | ||
| − | * CAS, most regular way with a need to provide login/password, useful for people who are out of Sugar | + | * CAS, most regular way with a need to provide login/password, useful for people who are out of Sugar Shell (and certificate based method does not work implicitly) and either casual visitor or not technical skilled enough to take care about user side certificates. |
| − | * | + | * Users certificates, useful for people who need to be authenticated from Sugar Shell when Sugar might do some routines under the hood. |
Revision as of 08:40, 20 September 2011
Summary
This is initiative to permit a user to access multiple SL resources while providing their credentials (such as userid and password) only once.
Resources to authenticate on
- http://wiki.sugarlabs.org
- http://git.sugarlabs.org
- http://bugs.sugarlabs.org
- http://activities.sugarlabs.org
- http://translate.sugarlabs.org
- https://obs.sugarlabs.org (Front-end HTTP API for OBS clients)
- https://packages.sugarlabs.org
Authenticate front-end methods
Preliminary list of possible front-end methods to authenticate users.
- For now https://obs.sugarlabs.org requires Basic HTTP Auth.
- CAS, most regular way with a need to provide login/password, useful for people who are out of Sugar Shell (and certificate based method does not work implicitly) and either casual visitor or not technical skilled enough to take care about user side certificates.
- Users certificates, useful for people who need to be authenticated from Sugar Shell when Sugar might do some routines under the hood.