[jboss-jira] [JBoss JIRA] (WFWIP-9) Elytron permission-set should throw exception for non-existent permission

[Farah Juma (JIRA)]

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

Farah Juma commented on WFWIP-9:
--------------------------------

[~mchoma] [~olukas] I've updated my feature branch to include the fix for this, the commit can be found here (I'll squash the commits before submitting the PR):

https://github.com/fjuma/wildfly-core/commit/2e940b86be81d8b9ad0fe5dd6c17f55610a208c1

Note that since the permission creation code is shared between permission sets and legacy permissions, this commit also ends up fixing the legacy equivalent of this issue (WFCORE-3796). Related to this, {{ConstantPermissionMapperTestCase}} in the WildFly testsuite needs to be updated as well (it currently attempts to configure a permission with an invalid module and then validates other permissions but this is no longer possible since configuring an invalid permission will now result in an exception being thrown):

https://github.com/fjuma/wildfly/commit/01c334a47a54ca6a35699668f57a4e693674cf53

> Elytron permission-set should throw exception for non-existent permission
> -------------------------------------------------------------------------
>
>                 Key: WFWIP-9
>                 URL: https://issues.jboss.org/browse/WFWIP-9
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: Security
>            Reporter: Ondrej Lukas
>            Assignee: Farah Juma
>              Labels: WFCORE-3596
>
> When non-existent permission (e.g. when there is a typo in class-name) is added to Elytron permission-set then exception should be thrown. It should throw exception for wrong class-name as well as wrong module.
> See issue WFCORE-3796 for more details.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)