i.e. they both contain both sss and ldap, with sss first. The client was
installed with the script generated by running ipa-advise config-redhat-
sssd-before-1-9 on the server. This script contains:
# Use the authconfig to configure nsswitch.conf and the PAM stack
authconfig --updateall
On 04/09/2015 11:19 AM, Guertin, David S. wrote:
If that works it means that you are not using SSSD on RHEL5 clients.
Please check your nsswitch and pam.conf to see what modules are actually
used.
Hmm. /etc/nsswitch.conf contains:
--
passwd: files sss ldap
shadow:
If that works it means that you are not using SSSD on RHEL5 clients.
Please check your nsswitch and pam.conf to see what modules are actually
used.
Hmm. /etc/nsswitch.conf contains:
--
passwd: files sss ldap
shadow: files sss ldap
group: files sss ldap
I have a mixed environment of RHEL 5 and RHEL 6 clients, and three RHEL 7 IPA
servers (one master and two duplicates). I'm trying to ensure that if one
server goes down, the remain server(s) will still allow logins. With the RHEL 6
clients this is easy -- the line
ipa_server = _srv_,
Guertin, David S. wrote:
I have a mixed environment of RHEL 5 and RHEL 6 clients, and three RHEL
7 IPA servers (one master and two duplicates). I'm trying to ensure that
if one server goes down, the remain server(s) will still allow logins.
With the RHEL 6 clients this is easy -- the line
On 04/08/2015 04:04 PM, Guertin, David S. wrote:
I have a mixed environment of RHEL 5 and RHEL 6 clients, and three
RHEL 7 IPA servers (one master and two duplicates). I'm trying to
ensure that if one server goes down, the remain server(s) will still
allow logins. With the RHEL 6 clients
