Well I think I can answer my own question partly.
I did a test and it works but the only problem is that
it is JBoss specific. Waiting to see if anyone else has any ideas.
I placed SecurityAssociation.getPrincipal()
and
SecurityAssociation.getCredential()
into an object that the mbean thread has access to
and before this thread goes to get a reference to the bean
I called
SecurityAssociation.setPrincipal(savedPrincipal);
SecurityAssociation.setCredential(savedCredential);
The bean then assumed the user that I pulled the principal from.
Is this legal?
I know it probably is not good practice to use JBoss internals.
jcl.
----- Original Message -----
From: "John Landers" <[EMAIL PROTECTED]>
To: "Jboss-User" <[EMAIL PROTECTED]>
Sent: Friday, March 01, 2002 4:52 PM
Subject: [JBoss-user] Q:Bean Security and JMX
> How would one do this:
>
> A Client makes a call to a EJB bean which
> ends up placing some information into
> a JMX MBean.
> This JMX MBean later on makes
> a call against the same EJB Bean (
> gets a hold of the bean just like the client did
> doing authentication etc. ) but
> needs to act as the same auth.'d user
> that put the information into this MBean
> in the first place.
>
> Is it possible to save off the auth. information
> and use it later?
>
> Hope this makes sense.
> Thanks for any information.
>
> jcl.
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
