[JBoss JIRA] (AS7-4951) adding Security Domain children(Authentication, Authorization, Audit, Mapping) by json not working.
11:31 a.m.
Simeon Pinder created AS7-4951:
----------------------------------
Summary: 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: CLI
Affects Versions: 7.1.2.Final (EAP)
Reporter: Simeon Pinder
Assignee: Alexey Loubyansky
-'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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:44 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Simeon Pinder commented on AS7-4951:
------------------------------------
Two things:
i)The json text doesn't look right in the description, but if you hit edit it's
available again.
ii)I did take the valid CLI command, and created CommandContextFactory with it and used
.toJsonString to make sure the json being sent matched what was expected. Unless the json
for 'add' is quite different from the json for 'write-attribute', then
this looks like a bug to me.
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: CLI
Affects Versions: 7.1.2.Final (EAP)
Reporter: Simeon Pinder
Assignee: Alexey Loubyansky
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:12 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky updated AS7-4951:
-----------------------------------
Component/s: Security
(was: CLI)
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: Alexey Loubyansky
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:16 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky updated AS7-4951:
-----------------------------------
Assignee: Anil Saldhana (was: Alexey Loubyansky)
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: Anil Saldhana
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:43 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse commented on AS7-4951:
---------------------------------------
You should try adding your commands in batch mode so they can be executed as a single
atomic unit and validated collectively: -
https://community.jboss.org/wiki/CLIBatchMode
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: Anil Saldhana
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:52 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Simeon Pinder commented on AS7-4951:
------------------------------------
I'll try to wrap this call in a composite operation and retest, but I have been
executing the 'add', 'read-attribute' and 'write-attribute'
operations atomically and it consistently fails as described only for 'add'. The
JSON request mirrors the same atomic operation via cli so I'm not sure if wrapping in
a composite is going to help here but I'll post back with an update shortly.
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: Anil Saldhana
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:08 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Anil Saldhana reassigned AS7-4951:
----------------------------------
Assignee: Stefan Guilhen (was: Anil Saldhana)
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:40 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Simeon Pinder commented on AS7-4951:
------------------------------------
No change after wrapping the 'add' operation as a single step in a composite/batch
operation via cli. I also thought about breaking the atomic 'add' into i)cd
address ii):add.... but that will not work because 'cd' is not a valid operation
to batch execution. Are there any other combinations that you want me to try or can you
reproduce this?
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:46 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse commented on AS7-4951:
---------------------------------------
This issue is starting to sound like it may be better to discuss within the forums.
On your last test did you add the adding of a login module to the batch? The error that
you are getting is that this has not been added so the operation needs to be within the
batch as validation will be performed at the end.
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:01 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:30 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-4951:
----------------------------------
Attachment: HttpClient.java
The attached client both adds and removes a security domain over HTTP - on adding the
authentication element at least one login module definition needs to be included.
I am however having a problem adding the module-options that I am still looking into.
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
Attachments: HttpClient.java
-'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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:10 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse commented on AS7-4951:
---------------------------------------
Stefan - Do you mind if I take ownership of this issue? The original complaint appears
resolved with a compound operation of two add steps within the compound operation to add
the domain definition but there is still a problem regarding the required type to define
the module options - I really need to discuss this further with Brian as there is a
backwards compatibility issue to this as well as an issue relating to validating happening
at different points.
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
Attachments: HttpClient.java
-'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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:35 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse resolved AS7-4951.
-----------------------------------
Fix Version/s: 7.1.3.Final (EAP)
7.2.0.Alpha1
Resolution: Rejected
Marking as rejected as the attached client demonstrates this is possible.
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
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
Attachments: HttpClient.java, HttpClient.java
-'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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:35 a.m.
[
https://issues.jboss.org/browse/AS7-4951?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-4951:
----------------------------------
Attachment: HttpClient.java
Ignore the last comments and see the latest HttpClient attached - a slightly different
form was needed to specify the module-options.
This client demonstrates that it is possible to fully define a security domain using json
over the HTTP management interface. For that reason I believe this issue can now be
resolved.
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
Attachments: HttpClient.java, HttpClient.java
-'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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5092
days inactive
5095
days old
13 comments
4 participants
participants (4)
-
Alexey Loubyansky (JIRA) -
Anil Saldhana (JIRA)
-
Darran Lofthouse (JIRA)
-
Simeon Pinder (JIRA)