Bug 154519 - GDM cannot login with LDAP
GDM cannot login with LDAP
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gdm (Show other bugs)
4.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
desktop-bugs@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-12 09:53 EDT by James Shanks
Modified: 2012-06-20 11:54 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 11:54:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description James Shanks 2005-04-12 09:53:43 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050322 Firefox/1.0.2 Red Hat/1.0.2-1.4.1

Description of problem:
I have configured LDAP on our RHEL4 server.  I can logon to the server from a local TTY session, I can logon from a Windows workstation with Samba, I can use LDAP on the server to validate the logon on a RH Linux 9 workstation, I can send email to users in the LDAP database, etc.  What I cannot do is logon using GDM on the LDAP server itself.


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

How reproducible:
Always

Steps to Reproduce:
1.  Setup LDAP on RHEL4
2.  Enable LDAP logon with authconfig
3.  Try to logon with a user in the LDAP database
  

Actual Results:  Login screen displays a Bad Username or Password Message

log has the following entries:
Apr 12 08:21:43 cruiser2005 gdm(pam_unix)[2766]: check pass; user unknown
Apr 12 08:21:43 cruiser2005 gdm(pam_unix)[2766]: authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
Apr 12 08:21:43 cruiser2005 gdm(pam_unix)[2766]: could not identify user (from getpwnam(jshanks))
Apr 12 08:21:43 cruiser2005 gdm-binary[2766]: Couldn't set acct. mgmt for jshanks


Expected Results:  should login.

Additional info:

A tty login gives the following:

Apr 12 08:20:31 cruiser2005 login(pam_unix)[5069]: check pass; user unknown
Apr 12 08:20:31 cruiser2005 login(pam_unix)[5069]: authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=
Apr 12 08:20:31 cruiser2005  -- jshanks[5069]: LOGIN ON tty1 BY jshanks
Comment 1 Jiri Pallich 2012-06-20 11:54:58 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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