[jboss-jira] [JBoss JIRA] (WFLY-6085) Wrong AdvancedADLdap mapping in ModulesMap

[Darran Lofthouse (Jira)]

     [ https://issues.jboss.org/browse/WFLY-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse resolved WFLY-6085.
------------------------------------
      Assignee: Darran Lofthouse
    Resolution: Won't Fix


Marking as 'Won't Fix' as this is in relation to the legacy security subsystem.  Although the fix is trivial it also needs to be backed by transformers.

> Wrong AdvancedADLdap mapping in ModulesMap
> ------------------------------------------
>
>                 Key: WFLY-6085
>                 URL: https://issues.jboss.org/browse/WFLY-6085
>             Project: WildFly
>          Issue Type: Bug
>          Components: Security
>            Reporter: Hynek Švábek
>            Assignee: Darran Lofthouse
>            Priority: Major
>
> There is wrong AdvancedADLdap mapping in ModulesMap.
> In ModulesMap is "AdvancedAdLdap", but in documentation is "AdvancedADLdap".
> https://github.com/jbossas/jboss-eap7/blob/7.x/security/subsystem/src/main/java/org/jboss/as/security/ModulesMap.java#L105
> https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0.beta/login-module-reference/#advancedadldap_login_module
> 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.
> {code}
> put("AdvancedAdLdap", AdvancedADLoginModule.class.getName());
> put("AdvancedADLdap", AdvancedADLoginModule.class.getName());
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)