geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GERONIMO-6015) JACC PolicyContextID conflicts
Date Fri, 17 Jun 2011 21:39:47 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks updated GERONIMO-6015:
-----------------------------------

    Attachment: GERONIMO-6015.diff

This is an alternate solution that adds all the permission info together for modules with
the same name.

> JACC PolicyContextID conflicts
> ------------------------------
>
>                 Key: GERONIMO-6015
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6015
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: security
>    Affects Versions: 3.0
>            Reporter: David Jencks
>            Assignee: Shawn Jiang
>             Fix For: 3.0
>
>         Attachments: GERONIMO-6015.diff
>
>
> cf rev 1136332.
> There's some kind of PolicyContextId collision, I think between a war module and an ejb
embedded inside.  The patch referred to tries to fix this by keeping 2 policy configurations
and changing the name of the ejb one. I think its only half complete though because I don't
see that the modified PolicyContextID is actually used by the ejb module at runtime. Instead
I think we can just add all the security configuration together for all the modules with the
same name.  However since I don't know for sure what is causing the original problem I don't
know how well this will work.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message