Admin console login fails with LDAP users first time only

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



When I restart the dirsrv-admin process on my 389 server, any attempt to login to the 389-console with my LDAP user ID fails with the following message:

“Cannot logon because of an incorrect User ID, Incorrect Password or Directory problem

HttpException:

Response: HTTP/1.1 401 Authorization Required

Status: 401

URL: http://389-srv1:9830/admin-serv/authenticate

 

After that I login with the built-in admin user, close the window, then log in with my LDAP user again and from then on it works (until the next time dirsrv-admin is restarted).

 

Here’s what I see in the error log (I added comments to show the sequence of events):

 

# Restart dirsrv-admin

[Tue Apr 15 12:02:56 2014] [notice] caught SIGTERM, shutting down

[Tue Apr 15 12:02:57 2014] [notice] SELinux policy enabled; httpd running as context unconfined_u:system_r:httpd_t:s0

[Tue Apr 15 12:02:58 2014] [notice] Access Host filter is: *.domain.com

[Tue Apr 15 12:02:58 2014] [notice] Access Address filter is: *

[Tue Apr 15 12:02:59 2014] [notice] Apache/2.2.15 (Unix) configured -- resuming normal operations

[Tue Apr 15 12:02:59 2014] [notice] Access Host filter is: *.domain.com

[Tue Apr 15 12:02:59 2014] [notice] Access Address filter is: *

 

# Failed login with rgroten

[Tue Apr 15 12:03:11 2014] [notice] [client 11.22.33.44] admserv_host_ip_check: ap_get_remote_host could not resolve 11.22.33.44

[Tue Apr 15 12:03:11 2014] [error] [client 11.22.33.44] user rgroten not found: /admin-serv/authenticate

 

# Successful login with admin

[Tue Apr 15 12:08:59 2014] [notice] [client 11.22.33.44] admserv_host_ip_check: ap_get_remote_host could not resolve 11.22.33.44

[Tue Apr 15 12:08:59 2014] [notice] [client 11.22.33.44] admserv_check_authz(): passing [/admin-serv/authenticate] to the userauth handler

 

# Successful login with rgroten

[Tue Apr 15 12:09:25 2014] [notice] [client 11.22.33.44] admserv_host_ip_check: ap_get_remote_host could not resolve 11.22.33.44

[Tue Apr 15 12:09:25 2014] [notice] [client 11.22.33.44] admserv_check_authz(): passing [/admin-serv/authenticate] to the userauth handler

 

Package versions:

389-ds-base-libs-1.2.11.25-1.el6.x86_64

389-ds-console-1.2.6-1.el6.noarch

389-adminutil-1.1.19-1.el6.x86_64

389-ds-base-1.2.11.25-1.el6.x86_64

389-admin-console-1.1.8-1.el6.noarch

389-ds-console-doc-1.2.6-1.el6.noarch

389-dsgw-1.1.11-1.el6.x86_64

389-console-1.1.7-1.el6.noarch

389-admin-1.1.35-1.el6.x86_64

389-admin-console-doc-1.1.8-1.el6.noarch

389-ds-1.2.2-1.el6.noarch

 

 

Thanks!

Ryan

 

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux