[ https://issues.jboss.org/browse/SRAMP-255?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-255: ----------------------------------------------- Eric Wittmann <eric.wittmann(a)redhat.com&gt; 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. -- 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