Description of problem:
If the email address is not updated correctly in the LDAP, then while logging to satellite webui with same username fails with error "Incorrect username or password" error.
But the error message from production log says "Email address is invalid"
Error message from log file:
2016-03-11 04:18:15 [I] Failed to save User 'sat6-user2' ["Email address is invalid"]
2016-03-11 04:18:15 [I] invalid user
2016-03-11 04:18:15 [I] Redirected to https://satellite.example.com/users/login
2016-03-11 04:18:15 [I] Completed 302 Found in 945ms (ActiveRecord: 2.7ms)
The error message in the webui is misleading, so the customer's expectation is to have a proper error message in WEB GUI like "XXX (here email) parameter(s) are not correct please correct it".
Version-Release number of selected component (if applicable):
Satellite v 6.1.9
Always when the invalid email address is stored in the LDAP server.
Steps to Reproduce:
1. Create a user in LDAP with invalid email ie: user#domain
2. Setup LDAP authentication on the satellite server
3. Try to login as a LDAP user to the satellite webui.
User login fails with error "Incorrect username or password" error.
Correct error message should be displayed on the login page if any of the LDAP parameter is not set correctly.
Connecting redmine issue http://projects.theforeman.org/issues/14720 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/14720 has been closed
Verification version: Satellite 6.3 Snap 13
1. configure the ldap authentication
2. set the user email to invalid. I was using FreeIPA, that didn't let me to
set up the email incorrectly via WebUI, so I did this
ldapmodify -D "uid=admin,cn=users,cn=accounts,dc=example,dc=test" -w Secret123 -h ibm-dx360m4-01.rhts.eng.bos.redhat.com -f change-mail.ldif
3. try to login
Got: user created with info about invalid data and asking the user to update (see the screenhost)
Created attachment 1319934 [details]
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> For information on the advisory, and where to find the updated files, follow the link below.
> If the solution does not work for you, open a new bug report.