Bug 1134085
| Summary: | Loading LDAP roles fails when some principal doesn't have an LDAP record | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Vojtech Juranek <vjuranek> |
| Component: | Server | Assignee: | Tristan Tarrant <ttarrant> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Gencur <mgencur> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.1 | CC: | afield, gsheldon, jdg-bugs, mhusnain |
| Target Milestone: | CR1 | ||
| Target Release: | 6.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously in Red Hat JBoss Data Grid, user authentication failed with a NamingException because the principal containing the remote client's network address could not be located in the LDAP directory. As a result, when resolving the roles associated with a Hot Rod authenticated user against an LDAP directory, the list of principals included an InetAddressPrincipal which contained the network address of the remote client. This is fixed in JBoss Data Grid 6.3.1. The role resolution logic has been modified so that the network address principal (InetAddressPrincipal) is not included in the list of principals that are verified against the LDAP directory. As a result, the role resolution of users authentication over Hot Rod works as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-01-26 14:04:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vojtech Juranek
2014-08-26 19:29:36 UTC
Adding to the JDG 6.3.1 payload to be reviewed |