Ben,
logoutURL is where cas will send the logout request (BACK_CHANNEL) or redirect
(FRONT_CHANNEL). Default is the url used during login.
With back channel logout, cas sends a logout request to logoutURL. Your cas
client has to process the request and perform the logout action. Check you cas
c
Hey all!
I have the same conclusion as Patryk. I built a CAS 7.1.1 recently with a
minimal set of overlays to actually try out form_post. Turns out, even
though I get HTTP POST on my redirect url instead of an HTTP GET, but there
is no data in the POST and the actual token value comes as an URL
This might be a long shot but have you tried to URL encode the entity ID if
that's what you are putting in the serviceID? For example: https%3A%2F%
2Fconncoll.reclaimhosting.com. We are not yet using CAS for SAML2 so just
a guess as I know the MDQ endpoint needs it that way.
On Mon, Oct 28, 2024
But from the
https://apereo.github.io/cas/7.0.x/installation/Logout-Single-Signout.html#casslodisabledPropertyConfig
page, it appears under the "Service Endpoint for Logout Requests" section,
if I set my logoutURL field to my application's log out, it CAS can get the
app to logout? Am I misund
I am currently trying to authenticate with X509 while using Redis as the
ticket caching registry and I get this error:
2024-10-31 17:46:44,719 ERROR
[org.apereo.cas.web.flow.DefaultSingleSignOnBuildingStrategy] -
org.apereo.cas.authentication.DefaultAuthentication["credentials"]->java.util.Arra
