Bug 102322 - Unable to ssh to box with LDAP authentication enabled via PAM
Summary: Unable to ssh to box with LDAP authentication enabled via PAM
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: openssh
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-13 20:14 UTC by Keith Sharp
Modified: 2007-04-18 16:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-04-15 18:56:14 UTC
Embargoed:


Attachments (Terms of Use)

Description Keith Sharp 2003-08-13 20:14:38 UTC
Description of problem:

The default config of sshd means that if you enable LDAP Authentication using
authconfig you cannot connect using ssh, but you can login at the console or by
telnet.  The default sshd_config file should be changed to to allow ssh logins
to be authenticated (via PAM) against an LDAP directory.


Version-Release number of selected component (if applicable):

openssh-3.5p1-6.9

How reproducible:

Always

Steps to Reproduce:
1. Setup LDAP directory with user objects etc
2. Run authconfig to configure PAM and NSS to use LDAP
3. Try to ssh to system using userid stored in LDAP
4. Unable to login
    
Actual results:

Unable to login.

Expected results:

Should be able to login.

Additional info:

I found the fix after some help on the shrike mailing list, my orginal question:

http://www.redhat.com/archives/shrike-list/2003-August/msg00457.html

and the successful answer:

http://www.redhat.com/archives/shrike-list/2003-August/msg00474.html

Comment 1 Shahms E. King 2004-04-15 16:30:14 UTC
That "fix" is not necessary.  The real fix, I suspect, was that you
restarted ssh after making the changes to the config file.

Comment 2 Nalin Dahyabhai 2004-04-15 18:56:14 UTC
Agreed.  When you enable LDAP in authconfig, /etc/nsswitch.conf has
"ldap" added to the list of sources for passwd and group information,
among other things.  This file is only read once by any given process.
 Because sshd forks to handle each new connection, new connections
don't "notice" changes to the file unless you restart the listening
daemon.  Marking worksforme.


Note You need to log in before you can comment on or make changes to this bug.