UConn is inverting what you describe -- instead of using CAS for webdav, etc, use a mechanism (Kerberos/LDAP) better suited for those non browser-based services, and then use CAS to easily extend those mechanisms to the browser environment.
-Matt On Wed, 2007-02-28 at 19:15 +0100, Stephane Bailliez wrote: > I'd be interested to know more bout how Rutgers or others are > integrating CAS for things like webdav, (s)ftp, shell accounts, etc... > in addition to web-application access. > > Is there any known location where to find background information for > this ? It would be very interesting to know the organizational > structure, datastore, infrastructure and application integrations (pam > anyone ?) > > Cheers, > > -- stephane > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas -- Matthew J. Smith <[EMAIL PROTECTED]> University of Connecticut UITS
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
