On Mon, Dec 8, 2014 at 11:01 PM, Vagrant Cascadian vagr...@debian.org wrote:
Not necessarily. LTSP fat clients just ssh to the server to get
authentication information as well as thin clientsq. Though applications
that require passwords (in particular, screen lockers) may require
additional
On Tue, Dec 9, 2014 at 2:04 AM, Ivan Mincik ivan.min...@gmail.com wrote:
Hi, GIS.lab project [1] is using LTSP Fat clients and LDAP
authentication. Server installation is done by Ansible [2] and client
configuration by custom LTSP plugins [3].
1 - http://imincik.github.io/gis-lab/
2 -
On 2014-12-09, Great Avenger Singh wrote:
I feel from Vagrant words we don't need LDAP authentication anymore
for LTSP setup or I am wrong somewhere?
Well, long term proper PAM integration to be able to use LDAP, SAMBA,
*SQL, Kerberos, etc. would be better, but there are workarounds/hacks
for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Arshpreet,
While helpful, that link is a bit dated and it doesn't deal at all with
secondary servers authenticating to the directory. I'm also biased
against any document that tells you to rm any original configuration file.
It's a fairly complex
On 2014-12-08, Lance Levsen wrote:
Here is the Debian way, https://wiki.debian.org/LDAP/PAM
If they're thin clients, getting it working on the server and
application servers is sufficient, if thick as well, you have to set up
NSS/PAM in their chroot too.
Not necessarily. LTSP fat clients
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.12.2014 17:28, Great Avenger Singh wrote:
Hi I want to setup LDAP for user login on
debian-64_amd(root-server) and debian-i386(two application
servers).
In my LDAP setup every user should be able to login from any
thin-client machine.
Hi I want to setup LDAP for user login on debian-64_amd(root-server)
and debian-i386(two application servers).
In my LDAP setup every user should be able to login from any
thin-client machine.
Do I need to go with procedure in the following link?
https://forum.zentyal.org/index.php?topic=12925.0
