Even worse, at redeployment of your webapp, wich I'm sure is not what you
need. The best you can do without using a custom object/permissions DB/DS is
at next login (when security context is populated) using automagic mapping
as in my previous reply.
(ppl correct me if I'm wrong here, I would like to be)
Wim
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: donderdag 21 augustus 2008 14:46
To: users_at_glassfish.dev.java.net
Subject: Re: Principal to Role Mapping
But does this really work on runtime or better expressed:
does it restrict the user at once (what i like to have) or at next login
> Now you need to modify the User's UserGroup
If restriction is at once, this would mean, that this solution must connect
the user table on every request
[Message sent by forum member 'hammoud' (hammoud)]
http://forums.java.net/jive/thread.jspa?messageID=294605
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net