Hi,
We assign usernames (principals) to roles dynamically, an administrator in our
application can create new users and assign roles, all information stored in a
database. We use the username to store what actions the user does. So I can't
use the run-as-principal as mentioned in the wiki docum
Annegret,
I don't think you read the link Scott posted correctly. You can use run-as
identity and yet retain principal by adding a run-as-principal. This my not
work for you if the principal is dynamic. If that is the case, then why not
just grant the principal the role at authorization time
Thanks for the clarification.
So this means if I need the name of the currently loggedin user in a nested
SessionBean I can't use the run-as identity.
Has this design changed or didn't the older JBoss versions (3.x, 4.0.3) work as
expected ?
Annegret
View the original post :
http://www.jbos
The nested creation uses the run-as identity then. This can be augmented with
additional roles.
http://wiki.jboss.org/wiki/Wiki.jsp?page=RunAsIdentityCreation
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926869#3926869
Reply to the post :
http://www.jboss.
There are 2 beans created: the first one is created as AdminUser, the principal
of the second one is AdminUser in case of JBoss4.0.3SP1 and anonymus in case of
JBoss4.0.4RC1.
Annegret
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926861#3926861
Reply to th
The run-as role takes precedence so what is the full call stack that is showing
different behavior? The log shows both anonymous and AdminUser
creating SubscriberSB.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926847#3926847
Reply to the post :
http://ww
