Shibboleth 3 and CAS integration

[John C. Pfeifer]

That was our prior configuration as well.

When we upgraded to Shib 3, we switched to the integrated CAS.  We modified the login.vm (and related files) to provide a visual continuity to to the old CAS and, with a little apache rewrite magic, supported the old URL’s so that no applications had to make any changes. No trauma to either the users or app admins (or ourselves).

> On Sep 24, 2018, at 5:21 PM, sherrera <sherrera at bradley.edu> wrote:
> 
> We are currently running CAS and Shibboleth 2 in production. Shibboleth2 is
> configured to use our CAS front end login page for users to authenticate. We
> are in the middle of upgrading to Shib 3. We have tested our attribute
> releases against testshib and things look to work as expected. What we can
> not figure out is how to replicate what we had before with using the CAS
> signin page. This is important to use because we are trying to train our
> users to not input their credentials into every site that requests them. 
> 
> I think I need to use the third-party ticket service but I'm not seeing or
> finding how to configure it. Is it still possible to accomplish this with
> Shib 3?
> 
> Thanks
> 
> 
> 
> --
> Sent from: http://shibboleth.1660669.n2.nabble.com/Shibboleth-Users-f1660767.html
> -- 
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


//
John Pfeifer
Division of Information Technology
University of Maryland, College Park