[
https://issues.jboss.org/browse/WFLY-2278?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on WFLY-2278:
-----------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug
1017786|https://bugzilla.redhat.com/show_bug.cgi?id=1017786]
This works for datasources, which is good news, but unfortunately it does not work for the
other big use case for this feature, JMS queues and topics. That is, these 2 commands are
insufficient to make Queues/Topics editable:
/core-service=management/access=authorization/constraint=application-classification/type=messaging/classification=jms-topic:write-attribute(name=configured-application,value=true)
/core-service=management/access=authorization/constraint=application-classification/type=messaging/classification=jms-queue:write-attribute(name=configured-application,value=true)
My guess as to the cause of this is that the relevant "Presenter" covers all
sorts of other stuff, i.e. Connection Factories, Security Settings, Address Settings,
Diverts, and these (correctly) cannot be configured to become "application
resources."
Deployer can't modify data source when datasources set as
application resources
-------------------------------------------------------------------------------
Key: WFLY-2278
URL:
https://issues.jboss.org/browse/WFLY-2278
Project: WildFly
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Ladislav Thon
Assignee: Brian Stansberry
Labels: rbac-filed-by-qa
Fix For: 8.0.0.CR1
When data sources are made application resources, deployer should be able to modify them.
This doesn't work, as opposed to e.g. mail sessions. For example:
{code}
/core-service=management/access=authorization/constraint=application-classification/type=datasources/classification=data-source:write-attribute(name=configured-application,
value=true)
{"outcome" => "success"}
[standalone@localhost:9990 /]
/subsystem=datasources/data-source=ExampleDS:write-attribute(name=jndi-name,
value="java:jboss/datasources/ExampleDS_XXX"){roles=deployer}
{
"outcome" => "failed",
"failure-description" => "JBAS013456: Unauthorized to execute
operation 'write-attribute' for resource '[
(\"subsystem\" => \"datasources\"),
(\"data-source\" => \"ExampleDS\")
]' -- \"JBAS013475: Permission denied\"",
"rolled-back" => true
}
[standalone@localhost:9990 /]
/core-service=management/access=authorization/constraint=application-classification/type=mail/classification=mail-session:write-attribute(name=configured-application,
value=true)
{"outcome" => "success"}
[standalone@localhost:9990 /]
/subsystem=mail/mail-session=java\:jboss\/mail\/Default:write-attribute(name=jndi-name,
value="java:jboss/mail/Default_XXX"){roles=deployer}
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{code}
I have a test case for this as a last commit in my branch
https://github.com/Ladicek/wildfly/commits/rbac (that is the commit called _RBAC test case
for application types_).
Brian, in case you are not the right assignee, please reassign.
--
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