Carl, TARGET is used with SAML 1.1 protocol (which Banner uses), service with CAS protocol(s). What is your service Id? It is odd that it works with service= and not TARGET=.
Ray On Thu, 2020-01-23 at 14:24 -0800, crdaudt wrote: We have had our Ellucian Banner service authenticating users through our CAS 5.2.2 service for several years, and are now attempting to migrate to our CAS 6.1.3 service. However, CAS does not recognize the JSON entry that we have in place for Banner. I believe the issue is related to the fact that the service ticket request includes the parameter "TARGET=..." rather than "service=..." in the URL. I.e.,: https://our.cas.server.edu/cas/login?TARGET=https%3A%2F%2Four.banner.server.edu%2FEmployeeSelfService%2Flogin%2Fcas rather than: https://our.cas.server.edu/cas/login?service=https%3A%2F%2Four.banner.server.edu%2FEmployeeSelfService%2Flogin%2Fcas If I manually replace 'TARGET=' with 'service=', the JSON entry is recognized and a service ticket is created. However, the banner service itself fails to do anything with the service ticket. Let me reiterate that the same JSON entry worked in our CAS 5 environment, but fails to work in our CAS 6.1 environment. Any ideas? Carl -- Ray Bon Programmer Analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected]<mailto:[email protected]> I respectfully acknowledge that my place of work is located within the ancestral, traditional and unceded territory of the Songhees, Esquimalt and WSÁNEĆ Nations. -- - 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/b5a155c336aafca5eb95dc1857d53bb86e17d649.camel%40uvic.ca.
