We use CAS in front of Shib, I wanted to move to CAS Shib, which as you say reduces complexity etc, I had done it all, got everything running, but couldn't get SAML1 working correctly, and a few of our providers still use SAML1 so had to back track and move to the unicorn shib-cas plugin with CAS 6.1.4.
If you only need SAML2 then CAS Shib works fine, but for SAML1 as well, you still need to use shibboleth. On Thursday, April 9, 2020 at 8:26:19 PM UTC+1, Jason Everling wrote: > > Has anyone moved from standalone Shib to the built-in CAS Shib? I am > looking to migrate ours, reduce complexity in our sso environment, we never > really used Shib as a login source, CAS was always redirected to by Shib > and I am curious on how you handled the new deployment. Did you just update > DNS and create rewrite rules so that requests are still routed correctly > without having to tell every service provider to update their urls? Was > there anything missing that you had to come up with a unique solution for > or was a straight forward migration? > > Thanks for any insights you might be able to share! > -- -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/2fdaa8f0-7000-46a8-a9e5-70c196164020%40apereo.org.
