portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor" <da...@bluesunrise.com>
Subject RE: Problem with implementing the PortalAuthentication/UserManagement interface
Date Mon, 19 Aug 2002 21:44:59 GMT
I committed your new method. Thanks!
For patches, try

cvs diff -u [module]

and then send us the output

-----Original Message-----
From: Amte, Amit [mailto:Amit.Amte@parexel.com]
Sent: Monday, August 19, 2002 8:19 AM
To: 'Jetspeed Developers List'
Subject: RE: Problem with implementing the
PortalAuthentication/UserManagement interface


David,
Thanks for the explanation.  I did extend the BaseJetspeedUser
to include by extra columns and it works great!
The Turbine_User table as we have defined it has additional
columns that are "read-only" and have been left out of the
security-schema.xml file.  The TurbineUserPeer.populateUserObject()
method fails in this case since it tries to get values for
all the columns in the Turbine_User table.
I modified this method so that it now ignores any column mismatches.
The attached file contains the modified method in its entirety.
HTH,
Amit
PS:  Will have to figure out how to get the diff output
     Till then .. please accept my apologies  ;-P

-----Original Message-----
From: David Sean Taylor [mailto:david@bluesunrise.com]
Sent: Friday, August 16, 2002 4:20 PM
To: Jetspeed Developers List
Subject: RE: Problem with implementing the
PortalAuthentication/UserManagement interface


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:
<mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:jetspeed-dev-help@jakarta.apache.org>



--
To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>


Mime
View raw message