Difference between revisions of "Infrastructure Team/Central Login"
Jump to navigation
Jump to search
(→Costs) |
|||
| Line 11: | Line 11: | ||
== Costs == | == Costs == | ||
| − | + | * To be accounted. <!- Be counted is a sign-less instrument, the sing depends on an intention (SL here is out of suspicions) and doers' professionalism (yep, thats the question). And for not being counted, there is only one option - not being counted anywhere, i.e., out of Login usecase at all. [[User:Alsroot|alsroot]] 12:46, 28 September 2011 (EDT) --> | |
== Resources to authenticate on == | == Resources to authenticate on == | ||
Revision as of 11:46, 28 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.
Benefits
- Single sign-on for all Sugar Labs services, and, in theory, for any Sugar related sites that want to get the benefits from Sugar Central Login (there is no need to be hosted on Sugar Labs' servers per se, only authentication for the target site will happen in a centralized manner).
- Centralized users database.
- Reuse users database not only for Web services, but also for shell accounts, for example.
Costs
- To be accounted. <!- Be counted is a sign-less instrument, the sing depends on an intention (SL here is out of suspicions) and doers' professionalism (yep, thats the question). And for not being counted, there is only one option - not being counted anywhere, i.e., out of Login usecase at all. alsroot 12:46, 28 September 2011 (EDT) -->
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-ends
- 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. The full featured option.
- OpenID authentication. Would be useful if particular service can link OpenID users and the ones got from CAS/LDAP. Without that, OpenID is just a standalone authentication method for particular service that does not relate to Central Login at all.
- Users certificates. Might be useful, e.g., for people who need to be authenticated from a Sugar Shell where Sugar might perform some authentication routines under the hood.
- Any method that can process authentication via LDAP, to reuse centralized users database only (no single sign-on).
Authenticate back-end
- ldap.sugarlabs.org