Difference between revisions of "Infrastructure Team/Central Login"

Revision as of 09:04, 28 September 2011

This is initiative to permit a user to access multiple SL resources while providing their credentials (such as userid and password) only once.

Single sign-on on all Sugar Labs services, and, in theory, on any Sugar related sites that want to get benefits from Sugar Central Login (there is no need to be hosted on Sugar Labs servers or so, only authentication will happen in centralized manner).
Centralized users database.
Reuse users database not only for Web services, but also for shell account, for example.

Preliminary list of possible front-end methods to authenticate users.

For now https://obs.sugarlabs.org requires Basic HTTP Auth.
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.
OpenID authentication.

@@ Line 5: / Line 5: @@
 == Benefits ==
-* [[wikipedia:Single_sign-on|Single sign-on]] on all Sugar Labs services and, in theory, on any Sugar related site that wants to get benefits from Sugar Central Login (there is no need to be hosted on Sugar Labs servers or so, only authentication will happen in centralized manner).
+* [[wikipedia:Single_sign-on|Single sign-on]] on all Sugar Labs services, and, in theory, on any Sugar related sites that want to get benefits from Sugar Central Login (there is no need to be hosted on Sugar Labs servers or so, only authentication will happen in centralized manner).
 * Centralized users database.
 * Reuse users database not only for Web services, but also for shell account, for example.