[
https://issues.jboss.org/browse/WFLY-1874?page=com.atlassian.jira.plugin....
]
Kabir Khan edited comment on WFLY-1874 at 8/16/13 2:59 PM:
-----------------------------------------------------------
I can reproduce the problem now, I see in my
https://gist.github.com/kabir/6230013 I had
left out the roles=maintainer header. Including that I see what you do. I'll document
a bit here what I see before digging in.
CLI to add the datasource:
{code}
subsystem=datasources/data-source=Test:add(jndi-name=java:/Test,jta=false,use-ccm=false,connection-url=url,driver-class=org.h2.Driver,driver-name=h2,user-name=user,password=pass,validate-on-match=false,background-validation=false,share-prepared-statements=false)
{code}
So if I start with a vanilla build containing just ExampleDS and then execute the CLI to
add the datasource, and then do:
{code}
/subsystem=datasources/data-source=*:read-resource-description(access-control=trim-descriptions,operations=true){roles=maintainer}
{code}
I only see ("data-source" => "ExampleDS") and
("data-source" => "*") in the list. 'ExampleDS' has
'Test' as an exception. '*' has no exceptions.
Then if I reload the server and execute the same r-r-d command I see
("data-source" => "Test"), ("data-source" =>
"ExampleDS") and ("data-source" => "*") in the list.
'ExampleDS' has 'Test' as an exception. '*' and 'Test'
have no exceptions. If I restart the server, I see the same output as following a reload.
was (Author: kabirkhan):
I can reproduce the problem now, I see in my
https://gist.github.com/kabir/6230013 I
had left out the roles=maintainer header. Including that I see what you do. I'll
document a bit here what I see before digging in.
CLI to add the datasource:
{code}
/subsystem=datasources/data-source=*:read-resource-description(access-control=trim-descriptions,operations=true){roles=maintainer}
{code}
So if I start with a vanilla build containing just ExampleDS and then execute the CLI to
add the datasource, and then do:
{code}
/subsystem=datasources/data-source=*:read-resource-description(access-control=trim-descriptions,operations=true){roles=maintainer}
{code}
I only see ("data-source" => "ExampleDS") and
("data-source" => "*") in the list. 'ExampleDS' has
'Test' as an exception. '*' has no exceptions.
Then if I reload the server and execute the same r-r-d command I see
("data-source" => "Test"), ("data-source" =>
"ExampleDS") and ("data-source" => "*") in the list.
'ExampleDS' has 'Test' as an exception. '*' and 'Test'
have no exceptions. If I restart the server, I see the same output as following a reload.
Inconsistent access control response structures
-----------------------------------------------
Key: WFLY-1874
URL:
https://issues.jboss.org/browse/WFLY-1874
Project: WildFly
Issue Type: Feature Request
Components: Domain Management
Reporter: Heiko Braun
Assignee: Kabir Khan
Fix For: 8.0.0.Beta1
Attachments: standalone-full-ha.xml
Compare the access control meta data for the different rrd() requests:
a)
https://gist.github.com/heiko-braun/6229507
b)
https://gist.github.com/heiko-braun/6229497
It happens on a system with two datasources confgured (ExampleDS & Test). You can
find the server config attached to this issues.
What we are looking for is a reliable response structure, without any ambiguity.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira