Re: Getting users and roles from external DB

2004-05-03 Thread David Sean Taylor
On May 3, 2004, at 10:03 AM, Carlos Yaconi Hitschfeld wrote:

Hi!
I'm implementing a portal that need to use the existent human 
resources DB (highly populated) to get the users and maybe the roles 
(this last thing depends on the information stored, because they don't 
want to re-write the user database nor the user-rol map, but if there 
is not enough information to map the roles, we must need to create 
that map).

As I saw in the documentation, all the information on this topic is 
Torque DB oriented, and I think isn't suitable for my requirements.

Wich could be the best strategy to manage the existing users and 
roles???
What class(es) should I override to implement my own users logic?
Must I have any other consideration about this topic??

Read this first:
http://portals.apache.org/jetspeed-1/security.html


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Getting users and roles from external DB

2004-05-03 Thread Carlos Yaconi Hitschfeld
Of course I read it!!
But I'm getting a little confused with that article because it says:
...  However Jetspeed is no longer coupled to the Turbine Security service
And below in that document, all the default security implementations are Turbine 
ones (which uses Torque), and the extending user Howto is Torque oriented too...



-Original message-
From: David Sean Taylor [EMAIL PROTECTED]
Date: Mon,  3 May 2004 13:20:39 -0400
To: Jetspeed Users List [EMAIL PROTECTED]
Subject: Re: Getting users and roles from external DB

 
 On May 3, 2004, at 10:03 AM, Carlos Yaconi Hitschfeld wrote:
 
  Hi!
  I'm implementing a portal that need to use the existent human 
  resources DB (highly populated) to get the users and maybe the roles 
  (this last thing depends on the information stored, because they don't 
  want to re-write the user database nor the user-rol map, but if there 
  is not enough information to map the roles, we must need to create 
  that map).
 
  As I saw in the documentation, all the information on this topic is 
  Torque DB oriented, and I think isn't suitable for my requirements.
 
  Wich could be the best strategy to manage the existing users and 
  roles???
  What class(es) should I override to implement my own users logic?
  Must I have any other consideration about this topic??
 
 Read this first:
 http://portals.apache.org/jetspeed-1/security.html
 
 
 
 -
 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]



Re: Getting users and roles from external DB

2004-05-03 Thread David Sean Taylor
On May 3, 2004, at 10:28 AM, Carlos Yaconi Hitschfeld wrote:

Of course I read it!!
Sorry, no need to yell at the support guy ;-) Im just trying to help

But I'm getting a little confused with that article because it says:
...  However Jetspeed is no longer coupled to the Turbine Security 
service
And below in that document, all the default security implementations 
are Turbine ones (which uses Torque), and the extending user Howto 
is Torque oriented too...


The database model is based on the Torque model, however it does not 
use any Torque classes to implement it.
If you want to implement your own User or Group or Role Management 
implementation, it does not have to be based on the default 
implementation.
However you do need to meet the required interfaces for services and 
object model classes.
Also, you can level your implementation, meaning that you can implement 
the User interfaces, but leave the default Group and Role 
implementations.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Getting users and roles from external DB

2004-05-03 Thread Carlos Yaconi Hitschfeld

-Original message-
From: David Sean Taylor [EMAIL PROTECTED]
Date: Mon,  3 May 2004 13:46:36 -0400
To: Jetspeed Users List [EMAIL PROTECTED]
Subject: Re: Getting users and roles from external DB

 
 On May 3, 2004, at 10:28 AM, Carlos Yaconi Hitschfeld wrote:
 
  Of course I read it!!
 
 Sorry, no need to yell at the support guy ;-) Im just trying to help

Sorry, It wasn't writed with the intention of a yell... just wanted to remark that 
before to post I read the docs..

 
  But I'm getting a little confused with that article because it says:
  ...  However Jetspeed is no longer coupled to the Turbine Security 
  service
  And below in that document, all the default security implementations 
  are Turbine ones (which uses Torque), and the extending user Howto 
  is Torque oriented too...
 
 
 The database model is based on the Torque model, however it does not 
 use any Torque classes to implement it.
 If you want to implement your own User or Group or Role Management 
 implementation, it does not have to be based on the default 
 implementation.
 However you do need to meet the required interfaces for services and 
 object model classes.
 Also, you can level your implementation, meaning that you can implement 
 the User interfaces, but leave the default Group and Role 
 implementations.

Thank you very much... and the last (I hope) question, Does all the 
classes(interfaces) needed to be overriden(implemented) are listed in that doc??

 
 
 
 -
 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]



Re: Getting users and roles from external DB

2004-05-03 Thread David Sean Taylor
On May 3, 2004, at 11:23 AM, Carlos Yaconi Hitschfeld wrote:
object model classes.
Also, you can level your implementation, meaning that you can 
implement
the User interfaces, but leave the default Group and Role
implementations.
Thank you very much... and the last (I hope) question, Does all the 
classes(interfaces) needed to be overriden(implemented) are listed in 
that doc??

Only the ones you want to override.
For example, you could override the UserManagement and 
PortalAuthentication implementations, and leave the others to the 
default implementations



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]