I have a system that uses LDAP. Originally I set this up as a stand-alone until all my company's security issues were mitigated. The problem is that on the GDM login, it does not display the name. I have this set up on our RHEL servers but not my laptop, so I log in as a local user and ssh to the servers. I can SU (or SUDO) to the LDAP user. I do have a local user set up with the same userid and group, but a separate home directory. I probably missed something somewhere.
On 06/22/2014 04:57 PM, Jerry Feldman wrote:
I have a system that uses LDAP. Originally I set this up as a stand-alone until all my company's security issues were mitigated. The problem is that on the GDM login, it does not display the name. I have this set up on our RHEL servers but not my laptop, so I log in as a local user and ssh to the servers. I can SU (or SUDO) to the LDAP user. I do have a local user set up with the same userid and group, but a separate home directory. I probably missed something somewhere.
I was able to get it to work, but when the console locks the password does not work. I have it set to autologin so the issue is with ddm.
On 06/24/2014 06:58 AM, Jerry Feldman wrote:
On 06/22/2014 04:57 PM, Jerry Feldman wrote:
I have a system that uses LDAP. Originally I set this up as a stand-alone until all my company's security issues were mitigated. The problem is that on the GDM login, it does not display the name. I have this set up on our RHEL servers but not my laptop, so I log in as a local user and ssh to the servers. I can SU (or SUDO) to the LDAP user. I do have a local user set up with the same userid and group, but a separate home directory. I probably missed something somewhere.
I was able to get it to work, but when the console locks the password does not work. I have it set to autologin so the issue is with ddm.
My solution was to create a local user with the same credentials of my LDAP user. If the network is up, then the login gets the exported home directory, if the network is down the local user gets a local home - such as when I power up before I bring the VPN online.
Jerry Feldman wrote:
My solution was to create a local user with the same credentials of my LDAP user. If the network is up, then the login gets the exported home directory, if the network is down the local user gets a local home - such as when I power up before I bring the VPN online.
A better solution would be to use sssd for authentication. It can cache credentials if the server is not available.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/24/2014 03:10 PM, Michael Cronenworth wrote:
Jerry Feldman wrote:
My solution was to create a local user with the same credentials of my LDAP user. If the network is up, then the login gets the exported home directory, if the network is down the local user gets a local home - such as when I power up before I bring the VPN online.
A better solution would be to use sssd for authentication. It can cache credentials if the server is not available.
If you use 'authconfig' to set up your LDAP configuration, it will automatically configure SSSD correctly.
-
Jerry Feldman -
Michael Cronenworth -
Stephen Gallagher