In previous versions of JBoss EAP 6, the JASPIC auth-module configuration in the security subsystem was ignoring the "module" attribute. This attribute tells PicketBox where to load custom auth-module classes from.
As a result, custom JASPIC auth-modules could not be configured as PicketBox was unable to determine the jboss module that should be used.
As the module attribute already exists in the security subsystem schema, the fix involved adding code in the security subsystem to handle this attribute, allowing PicketBox to correctly load custom modules.
As a result, users can now configure custom JASPIC auth-modules by using the "module" attribute to indicate the jboss-module that contains the custom module class.
Description of problem:
The JASPI auth-module configuration does not support a "module" attribute. This means that when using a custom JASPI module you will need to configure the application to depend on the custom module, make the JASPI module a global module or add the JASPI class to the picketbox module.
I think the JASPI auth-module should support a "module" attribute so that a user can specify which module contains a custom JASPI module.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Stefan Guilhen <firstname.lastname@example.org> made a comment on jira WFLY-2108
The module attribute exists in the XSD but is missing in the JASPIMappingModuleDefinition. I've updated the model and related transformers to allow configuration of custom auth-modules.
Verified on EAP 6.3.0.DR0.
Making public for visibility in 6.3.0 Release Notes.