this might help. - Test Policies: Ensure the attributeReleasePolicy is correctly defined in your service's JSON/YAML configuration. - Enable Debug Logs: Activate detailed logging for attribute release to see how CAS processes the policy. Update log4j2.xml in the WEB-INF/classes directory to set CAS logging levels to DEBUG for relevant components (org.apereo.cas). - Examine Logs: Look for errors or unusual behavior during service validation or authentication in catalina.out (if using Tomcat) On Tuesday, October 15, 2024 at 4:43:15 AM UTC-6 Joan Montal wrote:
> Hello, We are upgrading from version 6.4.6 to 7.1.1, but we are > encountering issues with the definition of services in OAuth > (OAuthRegisteredService). It is ignoring the attribute release policy > (attributeReleasePolicy) and ends up returning all the user's attributes. Has > anyone else faced the same issue? > -- - Website: https://apereo.github.io/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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/e712fe72-5c6e-4d09-8fbd-4eb9ecc9548en%40apereo.org.
