Infrastructure Team/Central Login: Difference between revisions
| Line 23: | Line 23: | ||
Preliminary list of possible front-end methods to authenticate users. | Preliminary list of possible front-end methods to authenticate users. | ||
* [[wikipedia:Central_Authentication_Service |CAS]], the most common method, with a requirement to provide login/password, is useful for people who are not arriving from a Sugar Shell instance (and so, Sugar's certificate-based method does not work implicitly for them), and for casual visitors or those wishing to avoid the technical work of taking care of user side certificates. | * [[wikipedia:Central_Authentication_Service |CAS]], the most common method, with a requirement to provide login/password, is useful for people who are not arriving from a Sugar Shell instance (and so, Sugar's certificate-based method does not work implicitly for them), and for casual visitors or those wishing to avoid the technical work of taking care of user side certificates. | ||
* Users certificates are useful for people who need to be authenticated from a Sugar Shell where Sugar might perform some authentication routines under the hood. | * Users certificates are useful for people who need to be authenticated from a Sugar Shell where Sugar might perform some authentication routines under the hood. | ||
* [http://en.wikipedia.org/wiki/OpenID OpenID] authentication. | * [http://en.wikipedia.org/wiki/OpenID OpenID] authentication. | ||
* Some services, e.g., https://obs.sugarlabs.org, requires Basic HTTP authentication by design. | |||
== Authenticate back-end == | == Authenticate back-end == | ||
* ldap.sugarlabs.org | * ldap.sugarlabs.org | ||