+++ This bug was initially created as a clone of Bug #1117846 +++ # add a new domain /subsystem=security/security-domain=test:add # setup auth with 2 "UsersRoles", modules. /subsystem=security/security-domain=test/authentication=classic:add(login-modules=[{ "code" => "UsersRoles", "flag" => "required", "module-options" => { "usersProperties" => "/home/tom/etc/UsersRoles/my-users.properties", "rolesProperties" => "/home/tom/etc/UsersRoles/my-roles.properties" }},{ "code" => "UsersRoles", "flag" => "required", "module-options" => { "usersProperties" => "/home/tom/etc/UsersRoles/my-users.properties", "rolesProperties" => "/home/tom/etc/UsersRoles/my-roles.properties" }}]) { "outcome" => "failed", "rolled-back" => true } Same thing happens with for example 2 LdapExt modules Modifying the xml manually and it will work fine though --- Additional comment from Tom Fonteyne on 2014-07-09 09:46:25 EDT --- tested on snapshot build of 2014-06-10 (also happens in wildfly)
Tom Fonteyne <tfonteyn> updated the status of jira WFLY-3604 to Resolved
ok.. me bad "attributes" => {"login-modules" => { ... "deprecated" => { "since" => "1.2.0", "reason" => "This attribute was replaced with sub resource" Using the sub resource works closing as not a bug