Bug 1117852

Summary: [GSS] (6.3.x) Using the CLI to setup a security domain with two login modules with the same "code" fails.
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Tom Fonteyne <tfonteyn>
Component: SecurityAssignee: Anil Saldhana <asaldhan>
Status: CLOSED NOTABUG QA Contact: Josef Cacek <jcacek>
Severity: high Docs Contact: Russell Dickenson <rdickens>
Priority: high    
Version: 6.3.0CC: anmiller, asaldhan, jcacek, myarboro, rdickens
Target Milestone: ---   
Target Release: EAP 6.3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1117846 Environment:
Last Closed: 2014-07-10 11:11:58 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:
Embargoed:
Bug Depends On: 1117846    
Bug Blocks:    

Description Tom Fonteyne 2014-07-09 13:58:18 UTC 
+++ 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)
Comment 1 JBoss JIRA Server 2014-07-10 11:10:58 UTC 
Tom Fonteyne <tfonteyn> updated the status of jira WFLY-3604 to Resolved
Comment 2 Tom Fonteyne 2014-07-10 11:11:58 UTC 
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