UserManagement

Differences between revisions 2 and 3
Revision 2 as of 2006-05-25 13:14:01
Size: 0
Editor: 196
Comment: specs go into blueprint from now on
Revision 3 as of 2007-05-09 10:30:17
Size: 1860
Editor: 195
Comment: first cut
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
##(see the SpecSpec for an explanation)

''Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.''

 * '''Launchpad Entry''': UbuntuSpec:edubuntu-user-management
 * '''Packages affected''':

== Summary ==

Edubuntu LTSP servers often have many users and the users and groups often change. Also, many LTSP servers are put into a Windows environment and user management needs to be easy in this situation.

== Rationale ==

In any Edubuntu setting, being able to manage users in on an LDAP or Active Directory server is key.

== Use Cases ==

Jane runs an Edubuntu server in her Windows network and wants to be able to have her students login with their AD user names.

Matt is about to start a new school year and needs to import a large number of users at the start of the new year.

== Scope ==

The users-admin tool and the system-tools-backend tools will need to be patched in order to talk to an LDAP or AD backend. Another tool will alos need to be written in order to setup the LDAP connection.

== Design ==

* we want to have a backend hooking into gnome-user-manager that connects to an ldap server
* a new capplet in the System->Administration menu that lets us select the ldap server to manage
  (use gnome-keyring of the local admin user to encrypt and save the credentials for the ldap servers admin user)
* if no values are set in the capplet we default to manage local users, else we default to the server thats set up
* a bulk import function should be added to import csv (should not be "in your face" since we likely only use it once a year if the school year starts for example)

== Implementation ==

== Outstanding Issues ==

== BoF agenda and discussion ==

----
CategorySpec

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Edubuntu LTSP servers often have many users and the users and groups often change. Also, many LTSP servers are put into a Windows environment and user management needs to be easy in this situation.

Rationale

In any Edubuntu setting, being able to manage users in on an LDAP or Active Directory server is key.

Use Cases

Jane runs an Edubuntu server in her Windows network and wants to be able to have her students login with their AD user names.

Matt is about to start a new school year and needs to import a large number of users at the start of the new year.

Scope

The users-admin tool and the system-tools-backend tools will need to be patched in order to talk to an LDAP or AD backend. Another tool will alos need to be written in order to setup the LDAP connection.

Design

* we want to have a backend hooking into gnome-user-manager that connects to an ldap server * a new capplet in the System->Administration menu that lets us select the ldap server to manage

  • (use gnome-keyring of the local admin user to encrypt and save the credentials for the ldap servers admin user)

* if no values are set in the capplet we default to manage local users, else we default to the server thats set up * a bulk import function should be added to import csv (should not be "in your face" since we likely only use it once a year if the school year starts for example)

Implementation

Outstanding Issues

BoF agenda and discussion


CategorySpec

Edubuntu/Specifications/UserManagement (last edited 2010-01-21 14:49:11 by 196-210-177-89-wblv-esr-3)