Bug 1301905 - Wrong AdvancedADLdap mapping in ModulesMap
Wrong AdvancedADLdap mapping in ModulesMap
Status: NEW
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Security (Show other bugs)
6.4.5
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: jboss-set
hsvabek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-26 05:41 EST by hsvabek
Modified: 2016-01-26 05:46 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description hsvabek 2016-01-26 05:41:17 EST
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.