Collecting Logs related to the Oauth2 Flow in Jira
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
By default, Oauth2 authentication produces little logging in Jira. When troubleshooting issues related to the oauth2 flow, however, its nice to be able to monitor the process from Jira's perspective. You can follow the steps below in order to increase oauth2 logging and monitor the authentication flow as data is returned and processed through your Jira environment
Environment
All supported Jira environments
Steps to Increase Logging
- Login to Jira as a Global Administrator
- Click on Settings > System > Logging and Profiling
- Click on "Configure Logging for Another Package"
- type in:
com.atlassian.oauth2 - select the logging level:
TRACE - click "Add"
- type in:
Where to Expect to See the Additional Logging Information
Jira will write the oauth2 related data captured to the atlassian-jira.log.
This package is noisy and should only be enabled while replicating the oauth2 related issue. Once testing completes, its strongly recommended to turn off this logger to prevent unnecessary data from filling up your log files.
Related Content
To learn more about Jira's utilization of Oauth2, please refer to: Jira Oauth2 Provider API