[overlord-issues] [JBoss JIRA] (SRAMP-255) Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on SRAMP-255:
-----------------------------------------------

Eric Wittmann <eric.wittmann at redhat.com> made a comment on [bug 1016591|https://bugzilla.redhat.com/show_bug.cgi?id=1016591]

A workaround as described above has been implemented.  The login module now looks for the Request first in the thread local variable.  If not found there, it will attempt to find the Request in the PolicyContext.  The former will only work if the application is configured to use the valve.

The following BZ exists to fix the PolicyContext bug:

  https://bugzilla.redhat.com/show_bug.cgi?id=1022069

Once that bug is fixed, then the PolicyContext approach will always work and the thread local valve will not be required.

In either case, the overlord apps should now have the valve configured, and thus should work in all cases.
                
> Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps
> ------------------------------------------------------------------------------------------------
>
>                 Key: SRAMP-255
>                 URL: https://issues.jboss.org/browse/SRAMP-255
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> This is actually an EAP bug:
>   https://bugzilla.redhat.com/show_bug.cgi?id=1016591
> This JIRA issue tracks the workaround used in Overlord.  The workaround is only necessary until the EAP bug is fixed.

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