Troubleshooting Delays in the Authentication Progress
If the authentication takes longer than expected, it may be difficult to track down the bottleneck. To simplify this process, version 6.0.11 introduces a specific logger in the package
de.resolution.samlsso.progress
When this is set to DEBUG, each user's authentication can be traced in the log. You need to enable this logging on each of your data center nodes to see messages like in the example further below. We recommend logging in with a tracker, read here how to do that. After being logged in, you can see the node ID at the bottom of the page in Jira, Confluence etc. after the last colon. That way you know for which of the nodes you need to create a support zip for us or for inspecting these logs yourself.
These are some sample records
- 2023-09-20 18:28:11,407 DEBUG [http-nio-8080-exec-22 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log Incoming request to SamlSsoServlet
- 2023-09-20 18:28:11,461 DEBUG [http-nio-8080-exec-22 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Sending IdP selection page
- 2023-09-20 18:28:11,482 DEBUG [http-nio-8080-exec-22 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Writing to response
- 2023-09-20 18:28:13,500 DEBUG [http-nio-8080-exec-5 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log Incoming request to SamlSsoServlet
- 2023-09-20 18:28:13,556 DEBUG [http-nio-8080-exec-5 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Initiating SAML-authentication
- 2023-09-20 18:28:13,579 DEBUG [http-nio-8080-exec-5 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Sending SAML message to IdP
- 2023-09-20 18:28:15,326 DEBUG [http-nio-8080-exec-30 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log Incoming request to SamlSsoServlet
- 2023-09-20 18:28:15,368 DEBUG [http-nio-8080-exec-30 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Loaded SAML message
- 2023-09-20 18:28:15,459 DEBUG [http-nio-8080-exec-30 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Calling LoginHandler
- 2023-09-20 18:28:15,459 DEBUG [http-nio-8080-exec-30 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Trying to load user
- 2023-09-20 18:28:15,494 DEBUG [http-nio-8080-exec-30 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Trying to find user in Directory
- 2023-09-20 18:28:15,495 WARN [http-nio-8080-exec-30 url: /plugins/servlet/samlsso] [samlsso.confluence.userauth.ConfluenceRemoteDirectoryAdapter] readApplyAutoGroups No value for directory attribute crowd.sync.group.membership.after.successful.user.auth.enabled on directory 98305:Confluence Internal Directory, returning NEVER
- -- url: /plugins/servlet/samlsso | userName: anonymous | referer: https://testidp.utopia.de/ | traceId: 818b5253cf447028
- 2023-09-20 18:28:15,496 DEBUG [http-nio-8080-exec-30 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Done finding user
- 2023-09-20 18:28:15,500 DEBUG [http-nio-8080-exec-30 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Authorizing user and establishing session
- 2023-09-20 18:28:15,531 DEBUG [http-nio-8080-exec-30 url: /plugins/servlet/samlsso] [de.resolution.samlsso.progress] log VUZPZ5GQ1CUHWR5 : Done handling SAML message
The ID behind the package name (VUZPZ5GQ1CUHWR5 in the example) correlates to the ID of the tracker that belongs to the authentication. You can find it at the bottom of our app's System & Support tab:
You can use the search function to either find the user that belongs to the ID or an ID for a user to search for in the logs.