Problem with implementing the PortalAuthentication/UserManagement interface

["Amte, Amit" <Am...@parexel.com>]

Hello,

I am trying to replicate the Turbine* security implementation
provided in the Jetspeed release (*.jetspeed.services.security.turbine.*)

Started off with the source from the above package
and modified them to work with the Torque OM objects I have in
my test project.  Also modified the JetspeedSecurity.properties file
to use the security framework classes that I created.

Everything works fine for the "anon" user.  I can trace the execution
and see that the (JetspeedUser)user object is being retreived and also
all the Roles and Permissions.

When I log in as a user (turbine/turbine) though, the login() method
always gets a "null" value back from the <code>user.getPassword()</code>
call.  This causes the authentication to fail and the user is kicked
out with a "Credential authentication failure".

Looking at the turbine implementation of the security framework,  I see that
TurbineRole, TurbineGroup and TurbinePermission implement the 
org.apache.jetspeed.om.security.Role/Group/Permission interfaces - but the 
TurbineUser _does not_ implement the JetspeedUser interface.
(I followed the same procedure with my OM objects)

Am I missing anything here?  The documentation says that I should be
extending
the JetspeedUser class .. but doesn't say how.

thanks,
Amit Amte
Perceptive Informatics

RE: Problem with implementing the PortalAuthentication/UserManagement interface

[David Sean Taylor <da...@bluesunrise.com>]

Hi Amit,

There are two different user objects:

1. org.apache.jetspeed.om.security.BaseJetspeedUser
2. org.apache.jetspeed.om.security.turbine.TurbineUser

The first is the normalized user object that implements the JetspeedUser
interface.
The second is only used in the Turbine security implementation as a Torque
peer.

If I understand correctly, you have extended the orginal Turbine schema, and
added some columns.
You then want to port this to the new Jetspeed security.
If thats the case, follow these steps:

1. modify the torque schema (security-schema.xml), add the new columns
2. build the system, the modified om.security.turbine peer objects will be
automatically generated
3. Extend the JetspeedUser interface to support these new columns, extend
BaseJetspeedUser to put the values into temp as you can see in other
accessor examples. The values will be automatically maintained by the
TurbineUserManagement service.

David

> -----Original Message-----
> From: Amte, Amit [mailto:Amit.Amte@parexel.com]
> Sent: Friday, August 16, 2002 11:52 AM
> To: 'Jetspeed Developers List'
> Subject: Problem with implementing the
> PortalAuthentication/UserManagement interface
>
>
> Hello,
>
> I am trying to replicate the Turbine* security implementation
> provided in the Jetspeed release (*.jetspeed.services.security.turbine.*)
>
> Started off with the source from the above package
> and modified them to work with the Torque OM objects I have in
> my test project.  Also modified the JetspeedSecurity.properties file
> to use the security framework classes that I created.
>
> Everything works fine for the "anon" user.  I can trace the execution
> and see that the (JetspeedUser)user object is being retreived and also
> all the Roles and Permissions.
>
> When I log in as a user (turbine/turbine) though, the login() method
> always gets a "null" value back from the <code>user.getPassword()</code>
> call.  This causes the authentication to fail and the user is kicked
> out with a "Credential authentication failure".
>
> Looking at the turbine implementation of the security framework,
> I see that
> TurbineRole, TurbineGroup and TurbinePermission implement the
> org.apache.jetspeed.om.security.Role/Group/Permission interfaces
> - but the
> TurbineUser _does not_ implement the JetspeedUser interface.
> (I followed the same procedure with my OM objects)
>
> Am I missing anything here?  The documentation says that I should be
> extending
> the JetspeedUser class .. but doesn't say how.
>
> thanks,
> Amit Amte
> Perceptive Informatics
>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>