Its certainly possible (I did it for a university that unfortunately ended up not open sourcing the code). At the moment it requires some custom flow actions and integration with the Java CAS Client (which luckily is already included via Spring Security)
On Mon, Aug 1, 2011 at 10:12 AM, John Field <[email protected]> wrote: > Hi all, > > I am currently running CAS 3.4.8, and I would like to have my CAS server > trust the login performed at another CAS server (3.4.2). That is: > > App A trusts CAS A (3.4.8). > App B trusts CAS B (3.4.2). > > I would like to have CAS A accept a service ticket issued by CAS B, as > proof of good authentication, and then have CAS A issue a TGT/ST for > application A. > > Is there any native support for this type of deployment? i.e. can I > accomplish this entirely through configuration, or would this require > writing custom code? > > We can make the simplifying assumption that the user population is the > same, i.e. both CAS servers share a common OpenLDAP back end, so there is no > worry about username collisions. > > Thanks, > John Field > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
