[jboss-jira] [JBoss JIRA] (WFLY-1980) Revisit priviledges for /core-service=management/access=authorization

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803654#comment-12803654 ] 

Brian Stansberry commented on WFLY-1980:
----------------------------------------

This is simple. The constraint was only being applied to 1 attribute in the JMX subystem!
                
> Revisit priviledges for /core-service=management/access=authorization
> ---------------------------------------------------------------------
>
>                 Key: WFLY-1980
>                 URL: https://issues.jboss.org/browse/WFLY-1980
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Brian Stansberry
>             Fix For: 8.0.0.Beta1
>
>
> It seems the access control resources (/core-service=management/access=authorization) are addressable by the monitor role:
> {noformat}
> [standalone at localhost:9990 /] /core-service=management/access=authorization:read-resource(){roles=monitor}
> {
>     "outcome" => "success",
>     "result" => {
>         "provider" => "simple",
>         "use-realm-roles" => false,
>         "constraint" => {
>             "application-classification" => undefined,
>             "sensitivity-classification" => undefined,
>             "vault-expression" => undefined
>         },
>         "role-mapping" => {"SuperUser" => undefined}
>     }
> }
> {noformat}
> I think it should be 'addressable=false' for anybody except SuperUser and Administrator

--
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