Difference between revisions of "Unified sign on"
From Apache OpenOffice Wiki
(→Goal Statement (Draft)) |
(adding user requested tasks) |
||
| Line 3: | Line 3: | ||
* ... | * ... | ||
| + | ;Communication | ||
| + | Subject:Unified sign on/Federated Identity | ||
| + | |||
| + | dev@openoffice.org | ||
| + | |||
| + | dev@website.openoffice.org | ||
= Project = | = Project = | ||
| Line 13: | Line 19: | ||
== In Scope (Draft) == | == In Scope (Draft) == | ||
| − | + | [[ Infrastructure_Requirements | OOo Infrastructure Requirements ]] | |
== Goal Statement (Draft) == | == Goal Statement (Draft) == | ||
| Line 19: | Line 25: | ||
| + | == Todos == | ||
| + | *details on Role model required and additional aspects from others than CEE | ||
| + | |||
| + | *Hopefully i extract correctly common ideas/suggestions from mailing;-) | ||
| + | **Investigate requests/suggestions with regard to [[ Infrastructure_Requirements | OOo Infrastructure Requirements ]] | ||
| + | ***http://openid.net/ http://www.mediawiki.org/wiki/Extension:OpenID <ref>http://website.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=9921</ref> | ||
| + | **Always fit into [[ Infrastructure_Requirements | OOo Infrastructure Requirements ]] and needs to be technical investigated | ||
| + | ***ssh public key authentication (Source Control) | ||
| + | ***Email access to bug-tracking <ref>http://website.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=9928 </ref> | ||
| + | |||
| + | References: <references/> | ||
| − | |||
= Documents = | = Documents = | ||
* http://wiki.services.openoffice.org/wiki/ESC_dashboard | * http://wiki.services.openoffice.org/wiki/ESC_dashboard | ||
* http://wiki.services.openoffice.org/wiki/Infrastructure_Requirements | * http://wiki.services.openoffice.org/wiki/Infrastructure_Requirements | ||
Revision as of 07:35, 3 July 2008
Contents
Team
- Gerd Weiss
- ...
- Communication
Subject:Unified sign on/Federated Identity
dev@openoffice.org
dev@website.openoffice.org
Project
Problem Statement (Draft)
There is no unified authentication procedure for registered OOo Users around all OpenOffice (satellite) Sites available. Therefor many Sites needs to maintain their own user base. Also registered OOo users needs to maintain several User Accounts.
Buisness Case (Draft)
Unified User bases will heavily support Community Members to work together on all relevant Community (satellite) Sites.
In Scope (Draft)
OOo Infrastructure Requirements
Goal Statement (Draft)
Regarding to OOo Infrastructure Requirements a common Interface/Infrastructure to access a centralized user Base for administrating Users, -rules and authentication.
Todos
- details on Role model required and additional aspects from others than CEE
- Hopefully i extract correctly common ideas/suggestions from mailing;-)
- Investigate requests/suggestions with regard to OOo Infrastructure Requirements
- Always fit into OOo Infrastructure Requirements and needs to be technical investigated
- ssh public key authentication (Source Control)
- Email access to bug-tracking [2]
- ↑ http://website.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=9921
- ↑ http://website.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=9928
