David Ramsey wrote:
> Turbine seems to implement but one type of user interface as specified in
> the user.class setting in the TurbineResources.properties file.
>
> I am looking at a situation in which there are two groups of users, one
> authenticated via SiteMinder, and the other authenticated via LDAP. The
> customer would like the Site Minder authenticated users to be plugged
> straight into their homepage without having to visibly login to Jetspeed. I
> think this is doable with a hidden post to Jetspeed's login action and
> specifying a SiteMinderUser class as the class to implement the user
> interface.
>
> However, this leaves me with the alternate set of users for whom I was
> working on an LDAPUser class.
>
> Is there any way to specify to Turbine the class to load, other than the
> default class specified in the properties file? In other words, I am looking
> for a way to choose between 2 User interface implementations. My first look
> at UserFactory seems to imply that it is always the class specified in the
> properties file.
This is perfectly doable. I think that you should use Turbine LoginUser action
for authenticating LDAP based users, and write a custom SessionValidator that
will try authenticating the user with SiteMinder (I haven't slightest idea
what could it be... some Jetspeed stuff?) and if authenticated, sticking
SiteMinderUser object into the session (just as LoginUser does).
Maybe I got something wrong, because I don't know JetSpeed, but for me it sounds
fairly easy.
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
