8,288
edits
Changes
Infrastructure Team/Central Login (view source)
Revision as of 16:12, 5 October 2011
, 16:12, 5 October 2011no edit summary
* Centralized users database.
* Centralized users database.
* Reuse users database not only for Web services, but also for shell accounts, for example.
* Reuse users database not only for Web services, but also for shell accounts, for example.
* (a side-benefit) Education about the risks of inter-networked services. Most people have little understanding of such risks, their significance, or appropriate protective behaviors.
== Costs ==
== Costs & Risks==
* To be accounted.
* To be accounted.
*: This point belongs to [[#Benefits|Benefits]] as well, e.g., if most of our services will use CAS, we will have only one, well controlled, access point. --[[User:Alsroot|alsroot]] 13:40, 28 September 2011 (EDT)
*: This point belongs to [[#Benefits|Benefits]] as well, e.g., if most of our services will use CAS, we will have only one, well controlled, access point. --[[User:Alsroot|alsroot]] 13:40, 28 September 2011 (EDT)
*:: There is an escalating intrusion/protection arms race on the Internet that challenges the most advanced providers of ethical services. Yes, we should seek to benefit from those efforts. --[[User:FGrose|FGrose]] 13:34, 5 October 2011 (EDT)
*:: There is an escalating intrusion/protection arms race on the Internet that challenges the most advanced providers of ethical services. Yes, we should seek to benefit from those efforts. --[[User:FGrose|FGrose]] 13:34, 5 October 2011 (EDT)
* What risks are there after signing on from a public workstation and leaving one's authentication cookie behind, or otherwise loosing one's cookie? What responsible efforts should we undertake to get the vulnerable community to participate more safely?
== Resources to authenticate on ==
== Resources to authenticate on ==