When checked, Jenkins will redirect to CAS after logging out the local user, in order to destroy the SSO session. Other CAS-enabled applications implementing Single Logout (SLO) may also opt to destroy their sessions.

If CAS is configured to follow logout redirects, it will automatically come back to Jenkins after destroying the SSO session.

Note that disabling this feature while making authentication mandatory will immediately redirect the user to CAS login after logging out of Jenkins, which in turn will validate the SSO session and re-authenticate the user in Jenkins. This could cause confusion for users who may think they can't logout.