[ http://issues.apache.org/jira/browse/GERONIMO-668?page=all ]
David Jencks closed GERONIMO-668:
---------------------------------
Resolution: Fixed
Implemented by adding a GeronimoCallerPrincipal interface, making
GeronimoUserPrincipal implement it, and returning it preferentially for
getCallerPrincipal. Reuse of GeronimoUserPrincipal may possibly lead to
confusion if there are several login modules all adding GeronimoUserPrincipal
instances, but this seems somewhat unlikely.
Sending
modules/security/src/java/org/apache/geronimo/security/ContextManager.java
Adding
modules/security/src/java/org/apache/geronimo/security/realm/providers/GeronimoCallerPrincipal.java
Sending
modules/security/src/java/org/apache/geronimo/security/realm/providers/GeronimoUserPrincipal.java
Adding
modules/security/src/test/org/apache/geronimo/security/ContextManagerTest.java
Transmitting file data ....
Committed revision 232906.
> Unable to determine username from EJB method
> --------------------------------------------
>
> Key: GERONIMO-668
> URL: http://issues.apache.org/jira/browse/GERONIMO-668
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M4
> Reporter: Ivan Dubrov
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> When calling EJB method from the Web module some important security context
> information (username) is lost. It is impossible to determine caller user
> name from the EJB method. EJBContext.getCallerPrincipal().getName() returns
> something like this:
> [org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal: manager]
> Note that only group name can be determined from this string or from the
> EJBMethod.getCallerPrincipal().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
