[jboss-jira] [JBoss JIRA] (WFLY-2295) Role mappings created through the CLI do not use formal role names

[Darran Lofthouse (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse resolved WFLY-2295.
------------------------------------

    Fix Version/s: 8.0.0.CR1
       Resolution: Duplicate Issue


For WFLY-2270 the underlying issue there was that role mappings could exist that do not correspond to either a standard role or to a scoped role, the solution on that issue is: -
 - Only accept role mappings where the name specified is equal using a case sensitive comparison to either a standard role or to a previously defined scoped role.
 - At the same time we will also prevent the removal of a scoped role if the role mapping still exists.

As a result it will no longer be possible to define roles in the CLI that do not use the formal role names.

                
> Role mappings created through the CLI do not use formal role names
> ------------------------------------------------------------------
>
>                 Key: WFLY-2295
>                 URL: https://issues.jboss.org/browse/WFLY-2295
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Harald Pehl
>            Assignee: Darran Lofthouse
>             Fix For: 8.0.0.CR1
>
>
> When creating a role mapping through the CLI using a non-formal role name like "AUDITOR", that role name is used as-is in the persistent configuration: 
> {code}
> cd /core-service=management/access=authorization
> ./role-mapping=AUDITOR:add
> ./role-mapping=AUDITOR/include=johndoe:add(name=johndoe,type=user)
> {code}
> The persistent configuration should map non-formal role names to formal role names, as other management clients (the console) rely on the formal names.

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