Bug 1301905 - Wrong AdvancedADLdap mapping in ModulesMap
Summary: Wrong AdvancedADLdap mapping in ModulesMap
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Security
Version: 6.4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: jboss-set
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-26 10:41 UTC by hsvabek
Modified: 2019-08-19 12:45 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:45:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description hsvabek 2016-01-26 10:41:17 UTC
There is wrong AdvancedADLdap mapping in ModulesMap.
In ModulesMap is "AdvancedAdLdap", but in documentation is "AdvancedADLdap".
https://github.com/jbossas/jboss-eap/blob/144d1d15f94f19914e4230601366adc22473c846/security/subsystem/src/main/java/org/jboss/as/security/ModulesMap.java#L105

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Security_Guide/index.html#topic4732_advancedadldap

We suggest some like this for backward compatibility:
Add one extra mapping to ModulesMap with right mapping and leave there old mapping too. Some old app can use this old wrong mapping.

put("AdvancedAdLdap", AdvancedADLoginModule.class.getName());
put("AdvancedADLdap", AdvancedADLoginModule.class.getName());


Note You need to log in before you can comment on or make changes to this bug.