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.
Thanks,
David Ramsey
==============================================================
"Always listen to experts. They'll tell you what can't be
done, and why. Then do it."
-- Lazarus Long, in Robert Heinlein's Time Enough for Love
==============================================================
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
