NetworkAuthClient

Differences between revisions 3 and 4
Revision 3 as of 2006-11-07 00:53:27
Size: 1500
Editor: 207
Comment:
Revision 4 as of 2006-11-08 19:29:16
Size: 2911
Editor: 207
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
BOF notes:  * '''Launchpad entry''': https://features.launchpad.net/distros/ubuntu/+spec/edubuntu-network-auth-client
 * '''Packages affected''':
Line 3: Line 4:
 * pam changes
 * nssldap changes
 * how do we mount home ?
== Summary ==
Line 7: Line 6:
ajmitch's authtool already cares for the first two points
all we have left for this spec is to find a proper way to mount /home on login
Authenticating edubuntu clients (workstations and ltsp servers) against an edubuntu network auth server.
Line 10: Line 8:
we will need kerberos integration, to integrate this a nameserver will be needed -> to be added to the -auth-server spec == Rationale ==
Line 12: Line 10:
a metapackage will be created that depends on the authtool package and pulls in the necessary kerberos bits To provide a centralized usermanagement in a school using edubuntu, an edubuntu network authentication server is implemented. To authenticate against such a server a certain client setup is required. This spec outlines what will be done to achieve client authentication on edubuntu ltsp servers and workstations.
Line 14: Line 12:
to change the password a tool is needed, this can either be a samba tool or a pam based one == Use cases ==
Line 16: Line 14:
for mounting home we will need to do a nfs export of /home from the server to mount that on login, for windows clients this needs also be done in parallel via samba Will is administrator at a highschool, he used to use an edubuntu LTSP server in one classroom to test the functionallity. Since the software convinced him he will now set up his whole school with edubuntu and set up an edubuntu network authentication server where he maintains the students accounts for the complete school and their homedirectories. After he installed the edubuntu-auth-client metapackage on all his workstations and ltsp servers all his students log in via the centralized service without problems.
Line 18: Line 16:
pam-mount needs to be extended to read the users home directory location from the ldap server where we store the information where to find the use
rs home.
== Scope ==
Line 21: Line 18:
pam-mount can do nfs mounts on login, Out of the box working authentication against an edubuntu network authserver.
Line 23: Line 20:
Packages to move to main: == Design and Implementation ==
Line 25: Line 22:
 * libpam-mount
 * libpam-ldap
 * libnss-ldap
 * libpam-ccreds
A metapackage called edubuntu-auth-client will be created.
It will depend on https://launchpad.net/people/ajmitch/+branch/network-authentication/authtool (which will provide the basic authentication functionallity) as well as on libpam-mount, libpam-ldap, libnss-ldap and libpam-ccreds.
Line 30: Line 25:
 * the edubuntu-auth-client package will install edsadmin and disable users-admin in the gnomemenu.
 * edubuntu-auth-client will ask for the desired domainname (field is prefilled with the provided domainname from the dhcp server) and for the ip address of the ldap server.
The libpam-mount, libpam-ldap, libnss-ldap and libpam-ccreds packages will move to main.
Line 33: Line 27:
There must be an additional preseed file for "networked-workstation" on the edubuntu CD that installs edubuntu-auth-client, the usual workstation preseed file will still do a local auth based install. Additionally a dependency on the edsadmin package (handled in edubuntu-auth-server) will be created. In the postinst of the edubuntu-auth-client the menu entry of the users-admin tool shipped gnome-system-tools will be disabled to avoid the confusion of having two user management tools.

The postinst of edubuntu-auth-client will ask for the desired domainname and for the ip address of the ldap server and preseed the authtool debconf values with it.

The edubuntu CD will get a new networked-workstation preseed file that pulls in the edubuntu-auth-client package. This way the user will still have the option to install a complete standalone workstation.

Edubuntu LTSP server installs will install the edubuntu-auth-client by default.

For mounting /home a nfs export in required on the authentication server, the edubuntu-auth-server will care for this.

The password tool of the "About Me" application shipped by default in ubuntu/edubuntu will be enhanced to operate properly with the users password on an ldap server.

== Unresolved issues ==

The pam-mount binary needs to be extended to read the users home directory location from the ldap server where we store the information where to find the users home.

----
CategorySpec

Summary

Authenticating edubuntu clients (workstations and ltsp servers) against an edubuntu network auth server.

Rationale

To provide a centralized usermanagement in a school using edubuntu, an edubuntu network authentication server is implemented. To authenticate against such a server a certain client setup is required. This spec outlines what will be done to achieve client authentication on edubuntu ltsp servers and workstations.

Use cases

Will is administrator at a highschool, he used to use an edubuntu LTSP server in one classroom to test the functionallity. Since the software convinced him he will now set up his whole school with edubuntu and set up an edubuntu network authentication server where he maintains the students accounts for the complete school and their homedirectories. After he installed the edubuntu-auth-client metapackage on all his workstations and ltsp servers all his students log in via the centralized service without problems.

Scope

Out of the box working authentication against an edubuntu network authserver.

Design and Implementation

A metapackage called edubuntu-auth-client will be created. It will depend on https://launchpad.net/people/ajmitch/+branch/network-authentication/authtool (which will provide the basic authentication functionallity) as well as on libpam-mount, libpam-ldap, libnss-ldap and libpam-ccreds.

The libpam-mount, libpam-ldap, libnss-ldap and libpam-ccreds packages will move to main.

Additionally a dependency on the edsadmin package (handled in edubuntu-auth-server) will be created. In the postinst of the edubuntu-auth-client the menu entry of the users-admin tool shipped gnome-system-tools will be disabled to avoid the confusion of having two user management tools.

The postinst of edubuntu-auth-client will ask for the desired domainname and for the ip address of the ldap server and preseed the authtool debconf values with it.

The edubuntu CD will get a new networked-workstation preseed file that pulls in the edubuntu-auth-client package. This way the user will still have the option to install a complete standalone workstation.

Edubuntu LTSP server installs will install the edubuntu-auth-client by default.

For mounting /home a nfs export in required on the authentication server, the edubuntu-auth-server will care for this.

The password tool of the "About Me" application shipped by default in ubuntu/edubuntu will be enhanced to operate properly with the users password on an ldap server.

Unresolved issues

The pam-mount binary needs to be extended to read the users home directory location from the ldap server where we store the information where to find the users home.


CategorySpec

Edubuntu/Specifications/NetworkAuthClient (last edited 2010-01-21 19:01:15 by 196-210-177-89-wblv-esr-3)