|Deletions are marked like this.||Additions are marked like this.|
|Line 30:||Line 30:|
| * system-tools-backend change to allow users-admin to admin network users
** if no values are set in the capplet we default to manage local users, else we default to the server thats set up
|* system-tools-backend change to allow users-admin to admin network users, which will display users from LDAP/AD users if a server is configured in the 2nd capplet and local users if not|
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: edubuntu-user-management
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.
In any Edubuntu setting, being able to manage users in on an LDAP or Active Directory server is key.
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.
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 second will also need to be written in order to setup the LDAP connection. A third tool will be for mass import of users into an AD or LDAP directory.
There are three pieces of work:
- system-tools-backend change to allow users-admin to admin network users, which will display users from LDAP/AD users if a server is configured in the 2nd capplet and local users if not
a new capplet in the System->Administration menu that lets us select the ldap server to manage which will use gnome-keyring of the local admin user to encrypt and save the credentials for the ldap servers admin user.
- a bulk import tool 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)
The system-tools-backend work will need to be in perl, as it is written in that. The two new tools will be written in Python.
Contact with upstream for system-tools-backends should be made in order to make certain that the patch to system-tools-backend will be accepted by them.