Bug 748568 - Attempting to update LDAP user's password fails with a blank error message
Attempting to update LDAP user's password fails with a blank error message
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core UI (Show other bugs)
4.2
Unspecified Unspecified
medium Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-24 16:41 EDT by Larry O'Leary
Modified: 2011-10-31 11:45 EDT (History)
1 user (show)

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


Attachments (Terms of Use)

  None (edit)
Description Larry O'Leary 2011-10-24 16:41:14 EDT
Description of problem:
If an administrative user attempts to update the password of an LDAP user (which should not be possible) the result is an error message "Operation failed. An error occurred" but the detailed message is blank. Digging into the server log file you can see:

Caused by: java.lang.IllegalArgumentException: You cannot set a password for an LDAP user.


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

How reproducible:
Always

Steps to Reproduce:
1. Login as rhqadmin
2. Select Administration -> Users
3. Select a user who has "LDAP Login?" set to "Yes
4. Enter a new password in the Password field
5. Enter the same new password in the Verify Password field
6. Click Save

  
Actual results:
Message is displayed "Operation failed. An error occurred" with empty details

Expected results:
Password field should not be editable/enabled
-- or --
Message is displayed "Operation failed. You cannot set a password for an LDAP user."
Comment 1 Mike Foley 2011-10-31 11:45:51 EDT
functionally this is working, but you can't update LDAP password through JON.  the error message could be better.

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