Chetan,
Also be aware that users are usually assigned to one or more security
roles ("user", "admin", etc.) Roles are defined in the
SECURITY_PRINCIPAL table along with the usernames, but are distinguished
from usernames by the FULL_PATH column. Usernames paths will contain
the "/user/" string but roles will be prepended with "/role/". (e.g.
/role/admin)
Roles are mapped to users in the SECURITY_USER_ROLE table which has just
two columns:
USER_ID: a foreign key to the SECURITY_PRINCIPAL table
corresponding
to the user.
ROLE_ID: a foreign key to the SECURITY_PRINCIPAL table
corresponding
to the role.
Users are assigned to multiple roles by defining multiple rows per user
in this table.
Oh, and if you want to store user information beyond username/password
(i.e. user profiles), note that this information is considered a user
preference and is stored in the PREF-NODE table.
Hope this helps,
James Winburn
-----Original Message-----
From: Michael Binette [mailto:[email protected]]
Sent: Wednesday, December 31, 2008 6:45 AM
To: Jetspeed Users List
Subject: Re: Accessing Jetspeed Database
The username is in SECURITY_PRINCIPAL along with names of groups and
roles.
You will notice that the CLASSNAME column will have a value of
org.apache.jetspeed.security.InternalUserPrincipalImpl for all users.
Or,
you can look at the FULL_PATH column and see that all user rows start
with
/user/.
I don't think the user name is saved anywhere else in its plain form
while
adding a new user.
--
Michael
On Wed, Dec 31, 2008 at 5:43 AM, Chetan Patel
<[email protected]>wrote:
>
> Hi Rob,
>
> Thanks for suggestion.
>
> The first solution is easy.
>
> I have see the all table but I am not able to find out which table is
use
> for storing user information in jetspeed.
>
> Please help me.
>
> Thanks again for help.
>
> --Chetan Patel
>
>
>
>
> Roberto Rossi-3 wrote:
> >
> > I think you can:
> >
> > 1) write a trigger of Jetspeed user tables to update to your own
table
> > whenever new records are inserted or when some records are updated,
in
> > this way you have not to change j2-admin source code.
> > To use triggers you should have mysql version 5.0.2 or greater, see
> > http://dev.mysql.com/doc/refman/5.0/en/triggers.html for more
details.
> > 2) modify j2-admin source code to adapt it to your needs
> >
> > I think the 1) approach is simples even if less elegant. Obviously
check
> > your mysql version
> >
> >
> >
> > ROb
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail:
[email protected]
> >
> >
> >
>
> --
> View this message in context:
>
http://www.nabble.com/Accessing-Jetspeed-Database-tp17626623p21229679.ht
ml
> Sent from the Jetspeed - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
