Having CAS handle local "private" passwords is possible but opens up a wide range of issues including namespace collision (i.e. the private username is the same as someone else's username) as well as the fact that if CAS is handling "private" passwords it can no longer initiate a SSO session since private passwords/usernames are not global.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Tue, Sep 23, 2008 at 4:29 PM, Serge Goldstein <[EMAIL PROTECTED]>wrote: > This is my first post to the list, so apologies if I am asking something > that has already been answered (is there a searchable archive?). > > We are looking to CASify an application that, in addition to accepting > institutional userids/passwords, also accepts "private" passwords (locally > defined to the application). Is there a way to have CAS handle that > directly, or do we need to create a "click here to login to CAS/ click here > to login locally" set of buttons? > > Serge Goldstein > Princeton University OIT > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
