Bug 753769 - Login issues with RHQ
Summary: Login issues with RHQ
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.2
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 750240
TreeView+ depends on / blocked
 
Reported: 2011-11-14 12:57 UTC by Sunil Kondkar
Modified: 2013-08-06 22:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:23:47 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 994267 0 unspecified CLOSED LDAP login causes Invalid path was requested error to appear in server log 2021-02-22 00:41:40 UTC

Internal Links: 994267

Description Sunil Kondkar 2011-11-14 12:57:17 UTC
Description of problem:

Installed build#74 from release_jon3.x branch (https://hudson.qa.jboss.com/hudson/view/JON3%20Core/job/rhq-release/74/)

Below issues observed:

1. In the login screen, when i input username/password as rhqadmin/rhqadmin, it does not login and displays the message "The backend datasource is unavailable." in the UI. The server log displays below:

2011-11-14 14:49:29,652 ERROR [org.apache.struts.action.RequestProcessor] Invalid path was requested /Dashboard

User is able to login after clicking on the login button second time.

2. Navigated to Administration->System settings and configured LDAP properties. Logged out and tried to login as LDAP user.
it does not login and displays the message "The backend datasource is unavailable." in the UI. The server log displays below:

2011-11-14 15:09:21,742 ERROR [org.apache.struts.action.RequestProcessor] Invalid path was requested /admin/user/UserAdmin

Tried with different LDAP users but LDAP user login fails with the same error in server log.

LDAP configuration details:
Redhat Directory Server 8.2.0

Search Base: dc=rajantest
Username: cn=Directory manager
Password=Redhat123
Search Filter: objectclass=*
Group Search Filter: objectclass=groupofuniquenames
Group Member Filter: uniquemember
Login Property: uid
URL-> ldap://10.65.201.169:1389

LDAP Users:
sunil1/Redhat123
vijay1/Redhat123

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

build#74 from release_jon3.x branch (https://hudson.qa.jboss.com/hudson/view/JON3%20Core/job/rhq-release/74/)

Postgres Version: 8.4.2

How reproducible:
Always

Steps to Reproduce:

1. Install build#74 from release_jon3.x branch.
2. Enter rhqadmin/rhqadmin at RHQ login screen and click on Login button
(It doesn't login and displays the message "The backend datasource is unavailable.")
3. Click again on Login button. Login is successful.
4. Navigate to Administration->System settings and configure the LDAP properties.
5. Logout and try to login as LDAP user.
6. Login fails with error in server log - "Invalid path was requested /admin/user/UserAdmin"
  
Actual results:

1. rhqadmin login fails the first time, however succeeds second time.
2. Not able to login as LDAP user.

Expected results:

Should be able to login as rhqadmin and LDAP users.

Additional info:

Tested in previous builds. (Build#70 and Build#73 in release_jon3.x branch).  The issues are not obsevred in previous builds. I was able to login as rhqadmin the first time and LDAP login is successful. 

The login issues are reproducible only in build#74.

Comment 1 Heiko W. Rupp 2011-11-14 13:44:26 UTC
With a clean browser cache it is possible to login locally.

b376c0e in master re-enables LDAP logins.

Comment 3 Sunil Kondkar 2011-11-29 12:19:59 UTC
Verified on build#106 from release_jon3.x branch (From
https://hudson.qa.jboss.com/hudson/view/JON3%20Core/job/rhq-release/106/)

Verified that rhqadmin/local users and LDAP users are able to login to RHQ successfully.

Comment 4 Mike Foley 2012-02-07 19:23:47 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


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