[jboss-jira] [JBoss JIRA] Resolved: (SECURITY-552) Add option to parse username in LdapExtLoginModule
[
https://issues.jboss.org/browse/SECURITY-552?page=com.atlassian.jira.plug...
]
Marcus Moyses resolved SECURITY-552.
------------------------------------
Resolution: Done
3 new options were added:
parseUsername, usernameBeginString and usernameEndString.
when <module-option name="parseUsername">true</module-option> is
present, the login module will look for the two other options to determine the begin and
end of a substring of the username. For example, adding:
<module-option name="parseUsername">true</module-option>
<module-option name="usernameBeginString">cn=</module-option>
<module-option name="usernameEndString">,</module-option>
will cause a username cn=TheDuke,ou=JBoss,o=Red Hat to be parsed to TheDuke
(usernameBeginString and usernameEndString are also excluded of the substring).
Add option to parse username in LdapExtLoginModule
--------------------------------------------------
Key: SECURITY-552
URL: https://issues.jboss.org/browse/SECURITY-552
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JBossSX
Affects Versions: JBossSecurity_2.0.4.SP5
Reporter: Marcus Moyses
Assignee: Marcus Moyses
Fix For: JBossSecurity_2.0.4.SP6
When LdapExtLoginModule is stacked with BaseCertLoginModule or some other scenario, the
username passed to LdapExtLoginModule can be a full DN. We need an option or options to
allow this name to be parseable in order to use just one attribute or part of the name.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira