`/status/health` is the recommended endpoint to retrive health check on 5.3.x . (https://apereo.github.io/cas/5.3.x/installation/Monitoring-Statistics.html)
However, if `/status/health` does not exists on 5.2.x, then your `/status` endpoint will do the monitoring job just fine for 5.2.x (might need to be careful when upgrading to 5.3.x). As for how to enable the endpoint, I have the following setup in my testing CAS server: cas.monitor.endpoints.status.enabled=true cas.monitor.endpoints.status.sensitive=false cas.monitor.endpoints.healthCheck.enabled=true cas.monitor.endpoints.healthCheck.sensitive=false You can see if the above properties is sufficient, and remove them line by line if you deem it too open. I do not know about /cas/statusxxx, it shows access error on my server. You can disable other core CAS monitoring in: https://github.com/apereo/cas/blob/v5.2.8/core/cas-server-core-monitor/src/main/java/org/apereo/cas/monitor/config/CasCoreMonitorConfiguration.java Set up a bean with the same name, disabling those monitoring in: final Set<Monitor> monitors = beans.entrySet().stream() .map(Map.Entry::getValue) .collect(Collectors.toSet()); And should be good to go. But... those monitoring are pretty lightweighted imo, I don't see why need to disable them, but your server your all :) However, be careful that in 5.3.x, the Monitoring is completely revampted, so if you change this in 5.2.x, you might need to reconfigure again in 5.3.x. Cheers! - Andy -- - 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/a4391a31-d217-423f-a6d0-9ebaf1a80840%40apereo.org.
