[
https://issues.apache.org/jira/browse/JS2-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Dam updated JS2-826:
---------------------------
Attachment: LdapMemberShipDaoImpl.patch
the method that parses the DN attribute value is extractLdapAttr . I added
nullpointer check after every usage of that method.
> Invalid DN values in group/role member attributes result in null pointer
> dereferences in the BasePrincipalImpl class
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JS2-826
> URL: https://issues.apache.org/jira/browse/JS2-826
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Security
> Affects Versions: 2.1.3, 2.2
> Reporter: Dennis Dam
> Priority: Minor
> Fix For: 2.1.3, 2.2
>
> Attachments: LdapMemberShipDaoImpl.patch
>
>
> If the users belonging to a role are determined by role attributes, so role
> to user mapping (and not the default, mapping users to roles), then an
> invalid DN in the role membership attribute will cause a user principal to be
> created with a NULL name. The reason for that is that the UID attribute (e.g.
> "CN=") cannot be found in the invalid DN value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
