> On Dec 17, 2015, at 12:09 PM, mozandy <[email protected]> wrote: > > The customer actually wants CAS for auth service which is working, but I can > use Shibboleth or whatever for federated saml 2.0 auth. I was hoping to just > use the same CAS instance and add the trustedHandler to the > authenticationManager map, but looks like I'll have to check for REMOTE_USER > in the header and maybe use a request param to determine if the user should > be auth'd via Shibboleth or CAS. So, there's no standard way to add saml 2.0 > federation to a CASified app?
It seems to me you are trying to handle an app side issue, CAS protocol vs SAML protocol by mixing up where you resolve authentication. Either you fix the app and allow both CAS endpoint authentication and SAML endpoint authentication or you don’t. I don’t believe adjusting things at the authentication service layer, CAS Server vs Shibboleth IdP, is relevant to your issue as it stands. You need to focus on your local problem at hand and try to solve your issue there rather than re invent the entire AuthN/Z flow. Conceptually I can think of an app that would have two entry points one for CAS based authN and one for SAML2 based authN. In general though we have no idea how much freedom you have with the code base or the web layer that is involved in your situation(s). HTH.. -------- 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/.
