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.