Issue Summary

This issue relates to JRASERVER-79444, where there is insufficient log output during the authentication handshake with connected applications (for example, Confluence User Directory sync). When failures occur, such as an HTTP 500 response on GET /rest/usermanagement/1/group/membership, there is no targeted logging to indicate whether the failure is caused by credential validation, session state, allowlist evaluation, or request sequencing.

Steps to Reproduce

1. Configure Confluence to connect to Jira via Jira User Server (Administration → User Management → Jira User Server)
2. Trigger a Full Synchronization from Confluence
3. Observe an HTTP 500 on GET /rest/usermanagement/1/group/membership
4. Attempt to diagnose using Jira logs at default INFO level — no meaningful output is produced

Expected Results

Actual Results

There are no helpful logs at debug level. Will update as soon as I know more.
The below exception is thrown in the xxxxxxx.log file:

Workaround

(currently testing) Enable DEBUG on com.atlassian.crowd.directory, com.atlassian.crowd.manager, and com.atlassian.crowd.integration.
Required, if there is no workaround please state:

Environment:

• Related bug: JRASERVER-79444