> On Dec 16, 2015, at 11:42 AM, mozandy <[email protected]> wrote: > > We have a Python Pylons web app that uses CAS 4.x for SSO, calls back to > serviceValidate to validate token. etc. and now we have a need to federate > with outside orgs using SAML 2.0. Was looking at Shibbolizing a CAS and > building a Shibboleth SP in front of CAS looking at this: > https://wiki.shibboleth.net/confluence/display/SHIB2/Shibbolize+a+CAS+server, > but so far don't have that working. Looks like CASShib is for an older > version of CAS, so I'm guessing I should leave that alone? Potentially I'm > thinking of using Asimba > (https://sourceforge.net/p/asimba/wiki/Quickstart%20Asimba%20Server%20Baseline/) > for testing and configuring IdPs that need to use our service. As a newbie > to SAML and CAS, it would be nice to hear from folks with experience if this > seems reasonable or I'm completely confused. Are there best practices for > setting up federated SAML 2.0 with CAS 4.1.x. What's the best approach to > take a CASified app and make it federated ? Thanks for any tips and guidance > :-)
Andy, I just realized I totally read your request wrong, sorry. Your query is actually how to federate your particular application using SAML2 rather than how to deal with shibcas or other ways to consolidate a SSO authentication infrastructure. If the application is yours I would begin by taking a step back and reading the how to[1] at the shibboleth wiki. Also this seams more like a question you should move to the shibboleth mailing list rather than here. [1] https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPEnableApplication -------- thanks kevin.foote -- 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]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
