Bug 1301905

Summary: Wrong AdvancedADLdap mapping in ModulesMap
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: hsvabek
Component: SecurityAssignee: jboss-set
Status: CLOSED EOL QA Contact: Pavel Slavicek <pslavice>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4.5CC: anmiller, bdawidow, darran.lofthouse, pskopek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:45:46 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:

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());