689
edits
Changes
From SME Server
Jump to navigationJump to searchClient Authentication:Ubuntu (view source)
Revision as of 14:45, 5 November 2009
, 14:45, 5 November 2009no edit summary
winbind cache time=10
winbind cache time=10
Replace <WORKGROUP> above with the workgroup name of your SME server
Replace <WORKGROUP> above with the workgroup name of your SME server. Replace <ip of sme server> above with the internal network ip address of your SME server.
Replace <ip of sme server> above with the internal network ip address of your SME server.
Edit
Edit
Replace <SMESERVER> above with the samba name of your SME server. This will mount the users 'home' directory from SME into a directory called 'nethome' in their local home directory.
Replace <SMESERVER> above with the samba name of your SME server. This will mount the users 'home' directory from SME into a directory called 'nethome' in their local home directory.
===Login and Test===
Logout of Ubuntu.
Login as a valid SME server user on your system, just giving username and password. No need for DOMAIN/user as samba configured above to use the default workgroup
Authentication against SME should proceed and the user log in. A home directory on the local machine should be created as /home/DOMAIN/user, and a sub directory to that called 'nethome' mounted to the users home directory on the SME server. The mount point should also appear on the users gui desktop.
===Issues / ToDo===
The above was tested on a VirtualBox virtual machine. The login appears to stall after username and password entered due to the mount of the home directory, but this does complete after a little while. Appears to be due to NAT traversal and WINS lookup as VM is using NAT and a different subnet. Couldn't get bridged mode to work, and haven't installed on a dedicated machine on the same subnet to confirm. Login is a little slow therefore.
Haven't tested or altered the pam password configuration to see if password changes are handled correctly.
