Oleg, Scott,
What crossed my mind:
Could it have something to do with calling a method
on the home interface. Since that is a difference
between the Session bean and the entity bean.
the getCallerPrincipal() for the session bean is
called from within an "created" session bean.
The entity getCallerPrincipal() is performed within
one of the home methods of this entity bean.
Regards,
Cor.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Oleg Nitz
Sent: Sunday, February 25, 2001 00:29
To: JBoss-User
Subject: Re: [jBoss-User] Problems with Principal class propagation
Hi Cor,
IMHO, looks like a bug, should work as you expect.
Strange. I have the similar situation: my owm Principal
implementation, my own server login module, session bean calls entity
bean, and in the entity bean getCallerPrincipal() returns my
implementation.
Could you try the current CVS version?
Regards,
Oleg
On Saturday 24 February 2001 09:18, Cor Hofman wrote:
> Hi,
>
> I implemented my own Principal class to add some extra
> authorization methods.
>
> When I perform a the login and call a session bean everything looks
> fine. The getCallerPrincipal() inside a sessionbean returns
> my own Principal. This session bean then calls an entity bean.
> When the entity bean call getCallerPrinciple() it returns an
> original SimplePrincipal instance. I would expect the entity bean
> to return my own Principal as well. Why isn't that happening?
> I expected the new Principal class to be propagated automatically.
>
> I use a PRE2.1 build from the beginning of january.
>
> For both the session bean and the entity bean I added the famous
> two lines:
>
> <role-mapping-manager>java:/jaas/companion</role-mapping-manager>
>
> <authentication-module>java:/jaas/companion</authentication-module>
>
> to the container types I use for the session and the entity bean
> (in standardJboss.xml).
>
> I also modified the auth.conf to contain a companion section.
>
> companion {
> org.companion.security.ServerLoginModule required;
> };
>
> Furthermore I added this to the client auth.conf
>
> companion
> {
> org.companion.security.ClientLoginModule required
> multi-threaded="true"; };
>
> Any suggestion or hint on how to tackle this one are ver much
> appreciated.
>
> Greetings,
>
> Cor Hofman
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
