You can use basic auth for these endpoints, you would want to store the
password in a secure secrets file for the deployment.
cas.monitor.endpoints.endpoint.ssoSessions.access=AUTHENTICATED
spring.security.user.name=casuser
--- separate secrets file
spring.security.user.password={noop}Mellon
I'm looking at staying within the SPM for CAS. I'm a bit nervous as the EoL
for 6.5.x is slated for the end of December. It looks like 7.0.0-RC9 is
slated for 12/22. Is there any plans for extending the 6.6.x SPM date? How
many releases are generally left in SPM after a new version of CAS is
AM UTC-7 John Bergant wrote:
> I am trying to upgrade my *CAS* server to *6.3.3* from *6.2.8* and it
> seems the OAuth flow is not working after the upgrade. In *6.3.x* there
> was a feature added that cached registered services (here is the commit
> <https://github.com/ap
I am trying to upgrade my *CAS* server to *6.3.3* from *6.2.8* and it seems
the OAuth flow is not working after the upgrade. In *6.3.x* there was a
feature added that cached registered services (here is the commit
Hi all,
I maintain a CAS server, we have multiple services registered with
different configurations. Some of the services are registered with Front
Channel Logout. I have noticed that CAS will not redirect to the specified
service on logout if one of the Front Channel Logout Services has been
Hi All,
Is there any plans to update the Google Delegated OAuth flow to use the
Google OpenID endpoint to retrieve *profile* *information* since the Google
Plus endpoint is going to be deprecated in March? I know this would
require a change to pac4j or restructuring how the endpoint is
