[jboss-jira] [JBoss JIRA] (JBEE-142) JACC permissions with HTTP method exception list are not correctly implemented

[Shelly McGowan (JIRA)]

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

Shelly McGowan commented on JBEE-142:
-------------------------------------

https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/javax/security/jacc/jboss-jacc-api_1.4_spec/1.0.3.Final/
has been released inclusive of the above changes.
                
>  JACC permissions with HTTP method exception list are not correctly implemented
> -------------------------------------------------------------------------------
>
>                 Key: JBEE-142
>                 URL: https://issues.jboss.org/browse/JBEE-142
>             Project: JBoss JavaEE Spec APIs
>          Issue Type: Bug
>          Components: jboss-jacc-api
>    Affects Versions: JavaEE 6 Spec APIs 3.0.2.Final
>            Reporter: Stefan Guilhen
>            Assignee: Stefan Guilhen
>             Fix For: JavaEE Spec APIs 3.0.3.Final
>
>
> As reported by Josef Cacek: JACC 1.1 permissions WebResourcePermission and WebUserDataPermission with an HTTP method exception list as actions should provide the correct list instead of null when calling getActions() method on them. Look at section "3.1.3.4 - Example" of the JACC 1.1 specification.
> There is also a second problem related - WebUserDataPermission.parseActions(String) method should remove the exclamation mark from the actions local variable before calling
> {code} 
> Object[] methodInfo = WebResourcePermission.canonicalMethods(actions);
> {code}

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