[jboss-jira] [JBoss JIRA] (WFLY-5340) Unable to specify module when specifying custom JACC policy class.

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on WFLY-5340:
-----------------------------------------------

Vaclav Tunka <vtunka at redhat.com> changed the Status of [bug 1263336|https://bugzilla.redhat.com/show_bug.cgi?id=1263336] from POST to MODIFIED

> Unable to specify module when specifying custom JACC policy class.
> ------------------------------------------------------------------
>
>                 Key: WFLY-5340
>                 URL: https://issues.jboss.org/browse/WFLY-5340
>             Project: WildFly
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 10.0.0.Beta2
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>             Fix For: 10.0.0.CR1
>
>
> It is currently possible to specify the 'javax.security.jacc.policy.provider' system property, however it is not possible to specify a module.
> From the JACC specification: -
> _For each JRE of a J2EE 1.4 or later version Java EE application server, if the 
> system property 
> “javax.security.jacc.policy.provider
> ” is defined, 
> the application server must construct an 
> instance of the class identified by the 
> system property, confirm that the 
> resulting object is an instance of 
> java.security.Policy, 
> and set, by calling the 
> java.security.Policy.setPolicy
>  method, the resulting object as the 
> corresponding Policy object u
> sed by the JRE. _
> The specification only specifies that the system property identifies the class, it does not specify how.  
> In it's simplest form we should assume this is just a class name, in a more complex form we should allow the module to be specified.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)