[
https://jira.jboss.org/browse/EJBTHREE-913?page=com.atlassian.jira.plugin...
]
Carlo de Wolf resolved EJBTHREE-913.
------------------------------------
Resolution: Out of Date
This issue is reported against a version which is no longer maintained,
which means that it will not receive a fix. As a result we are closing
this bug.
If you can reproduce this bug against a currently maintained version of
JBoss EJB 3 please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
java.lang.IllegalStateException in
SessionContext::getCallerPrincipal()
-----------------------------------------------------------------------
Key: EJBTHREE-913
URL:
https://jira.jboss.org/browse/EJBTHREE-913
Project: EJB 3.0
Issue Type: Bug
Components: Security
Affects Versions: EJB 3.0 RC9 - FD
Environment: AS: jboss-4.0.5 (ejb3 Version EJB 3.0 RC7 - FD and EJB3 RC9 Patch
1)
OS: Windows, GentooLinux
Reporter: Mihail Druzinin
Attachments: Apache Tomcat_5.5.20 - Error report.htm, E3T1-client.zip,
E3T1-server.zip, E3T1-web1.zip, patch-SecurityAssociation
From HttpServlet I execute methods from stateless been.
All methods executed correctly with authorization.
When in method I try sessionContext.getCallerPrincipal(), then throws
java.lang.IllegalStateException: No valid security context for the caller identity
After see in jboss security module I find that in org.jboss.security.SecurityAssociation
getCallerPrincipal()
when used RunAsIdentity, it getted not from top of RunAsIdentity stack, but "for the
active run-as the previous caller has assumed":
Principal thePrincipal = peekRunAsIdentity(1); (SecurityAssociation.java:216).
After fixed that string to: Principal thePrincipal = peekRunAsIdentity(0), all start
work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira