Dave Brondsema wrote:
Using CAS gets rid of separate passwords, but not separate user
information. CAS does the authentication, but then Liferay still needs
its users table to store users' names, email addresses, etc.
I figured as much... after a lengthy struggle :)
I have a schedule job set to populate the Liferay users table with the
correct information for our users. I believe it is also possible to
write a Java class (or use one.. I can't remember if the portal comes
with one already) that creates/updates Liferay user info from LDAP
automatically whenever the user logs in.
I think I'll be going the "write my own class to automate this at login
time"-route. Doesn't look too complicated :)
I can't believe they haven't already implemented this... not that much
point in the CAS auth otherwise (from my point of view anyway)
Thanks anyway :)
--
Anna Pakkala
Vanhempi suunnittelija
Turun yliopiston ATK-keskus
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
