Bug #55450 | LDAP authentication not working for mapping roles in a user attribute | ||
---|---|---|---|
Submitted: | 21 Jul 2010 17:12 | Modified: | 17 Aug 2010 10:47 |
Reporter: | Leandro Morgado | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Server | Severity: | S3 (Non-critical) |
Version: | Monitor: 2.2.2.1730 | OS: | Any |
Assigned to: | Mark Matthews | CPU Architecture: | Any |
[21 Jul 2010 17:12]
Leandro Morgado
[21 Jul 2010 18:44]
Leandro Morgado
Hi Marcos, I have both versions running and tested map rolling as follows: 2.2.1.1721: * LDAP user, precreated in MEM dashboard, no role mapping: works, fetched password only from LDAP * LDAP user, non existent in MEM dashboard, role mapping with user attribute: works, fetched password and role from LDAP, automatically created an LDAP user in MEM dashboard upon first successful login * LDAP user, non existent in MEM dashboard, role mapping with LDAP groups and uniqueMember={0}: failed with user/password error 2.2.2.1730: * LDAP user, precreated in MEM dashboard, no role mapping: works, fetched password only from LDAP * LDAP user, non existent in MEM dashboard, role mapping with user attribute: failed with user/password error * LDAP user, non existent in MEM dashboard, role mapping with LDAP groups and uniqueMember={0}: works, fetched password and role from LDAP, automatically created an LDAP user in MEM dashboard upon first successful login
[17 Aug 2010 10:47]
MC Brown
A note has been added to the 2.2.3 changelog: Using LDAP authentication for mapping roles using user attributes would not authenticate correctly.