]
Simeon Pinder commented on AS7-4951:
------------------------------------
I just pinged you in #jboss-as7 with this response:
darranl: I did add the 'login-module' module component even in batch mode. I
don't think batching has anything to do with this issue. The only difference between
'add' and 'write-attribute' is the operation name. 'add' fails
when there is no component, but 'write-attribute' succeeds without problem and
successfully updates when there is an existing 'authentication=classic' component.
darranl: In both case the 'login-module' attribute is defined in the exact same
way and by the same json excerpt. The fact 'login-module' is valid for
'write-attribute' and not for 'add' is why I think this is a bug.
If you hit 'Edit' mode for this JIRA you will see the json excerpt being sent as
the raw json is being parsed as a macro above otherwise.
Does this help to clarify? I also think this is past a forum post because all the details
are already laid out here in a public jira. No?
adding Security Domain
children(Authentication,Authorization,Audit,Mapping) by json not working.
------------------------------------------------------------------------------------------------
Key: AS7-4951
URL:
https://issues.jboss.org/browse/AS7-4951
Project: Application Server 7
Issue Type: Bug
Components: Security
Affects Versions: 7.1.2.Final (EAP)
Reporter: Simeon Pinder
Assignee: Stefan Guilhen
Labels: rhq
-'Add' operation for Security Domain
children(Authentication,Authorization,Audit,Mapping) 'fails with JBAS014746:
login-modules may not be null'. The fail message is for Authentication specifically
..but the other nodes fail with matching provider-modules not be null,etc.
- Assumes there is a securityDomain of name 'testDomain3' with
cache-type='default'.
-Once the Security Domain child does exist 'read-attribute' and
'write-attribute' operations work as expected via json. This indicates to me that
the json values for 'login-modules' is sound but just not acceptable because of a
bug.
- The same 'add' operation, see below, via cli completes successfully.
/subsystem=security/security-domain=testDomain3/authentication=classic:add(login-modules=[{"code"=>"SecureIdentity","flag"=>"required","module-options"=>{"bindDn"=>"uid=ldapSecureUser,ou=People,dc=redat,dc=com"}}])
- This is what the json contents look like before being sent off to the server. Switching
'add' to 'write-attribute' works correctly once the node already exists.:
{
"operation" : "add",
"address" : [ {
"subsystem" : "security"
}, {
"security-domain" : "testDomain3"
}, {
"authentication" : "classic"
} ],
"name" : "login-modules",
"value" : [ {
"flag" : "required",
"code" : "Ldap",
"module-options" : {
"bindDn" : "uid=ldapSecureUser,ou=People,dc=redat,dc=com",
"bindPw" : "test126",
"allowEmptyPasswords" : "true"
}
} ]
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: