LX0-104 · Question #128
After configuring PAM and NSS to integrate with OpenLDAP, the SSH server refuses to authenticate users who are only in LDAP. What is the first step you should follow to debug this problem?
The correct answer is B. Restart the sshd service. After configuring PAM and NSS for OpenLDAP integration, if SSH authentication fails for LDAP users, the sshd service must be restarted to apply the new authentication settings. Services often need a restart to load updated PAM/NSS configurations.
Question
Options
- ARestart the pamd service.
- BRestart the sshd service.
- CRestart the nssd service.
- DAdd the Use_LDAP = yes parameter to sshd_config.
How the community answered
(30 responses)- A7% (2)
- B80% (24)
- C10% (3)
- D3% (1)
Why each option
After configuring PAM and NSS for OpenLDAP integration, if SSH authentication fails for LDAP users, the `sshd` service must be restarted to apply the new authentication settings. Services often need a restart to load updated PAM/NSS configurations.
`pamd` is not a standard service to restart; PAM configurations are loaded by applications that use PAM, such as `sshd`.
When PAM (Pluggable Authentication Modules) and NSS (Name Service Switch) configurations are changed to integrate with OpenLDAP, the `sshd` service needs to be restarted so it can load the updated authentication libraries and configurations to authenticate users correctly.
`nssd` (or `nscd` - Name Service Cache Daemon) might be restarted to clear caches, but `sshd` still needs to reload its own PAM configuration.
`Use_LDAP = yes` is not a standard or necessary parameter in `sshd_config` for OpenLDAP integration; PAM handles the LDAP authentication backend.
Concept tested: Restarting services after PAM/NSS changes
Source: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_level_authentication_guide/pam_configuring
Topics
Community Discussion
No community discussion yet for this question.