---
title: "EasySSO How to get the Logs"
canonical: "https://www.techtime-initiative.com/space/EasySSO/4522300/EasySSO%20How%20to%20get%20the%20Logs"
format: markdown
---
## Logs that TechTime support will need
### NTLM/Kerberos authenticators
For versions 4.12.0 and greater, admins can use the 'Test SSO' tab inside the NTLM/Kerberos configuration page to test and download log files that are specifically related to the login
For versions prior to 4.12.0 we will need jespa.log (steps 1-7) and the base application log e.g. atlassian-jira.log (step 8).
We may request a [HAR file](https://confluence.atlassian.com/kb/generating-har-files-and-analyzing-web-requests-720420612.html) too, but this doesn't happen often.
### SAML authenticators
For versions after 4.10.0, admins can use the 'Test SSO' tab inside SAML to test and download log files that are specifically related to the SAML Login.
For older versions or logins on client computers we will need the base application log e.g. atlassian-jira.log (step 8) and a [HAR file](https://confluence.atlassian.com/kb/generating-har-files-and-analyzing-web-requests-720420612.html)
### X.509 and HTTP Headers authenticators
we will need the base application log e.g. atlassian-jira.log (step 8) and ultimately any logs you may have on your proxy (since certificate headers and HTTP headers are supposed to be set by a trusted proxy, and only by that)
## Set the correct log levels
### Step 1: Navigate to the EasySSO advanced conguration
Click on the **Administration Cog** on the top right corner of the screen, and from the drop down menu select Add-ons
Locate and click on **EasySSO** under **TECHTIME ADD-ONS** on the left side of the screen
Click on the **Advanced Configuration** button on the top right corner (via NTLM/Kerberos in EasySSO 4.0+)
### Step 2: Set Jespa logs to Trace level
- Review the 'Enable Log4j logging' box. Make a note of the original setting and **uncheck** this box if it is checked.
- Set the 'Log Level' to **4 - Trace. **Make a note of the original setting.
- Once changes have been made, click** Save **
### Step 3: Set application logs to Debug level
Enable `DEBUG` level logging for the 'org.techtime' package. You will have to **add** logging for this package. If you are restarting you will have to add the package again.
Jira: Enable debug logging
See Atlassian docs: [How to set logging level for a package in Jira](https://confluence.atlassian.com/jirakb/how-to-set-logging-level-for-a-package-in-jira-629178605.html)
Use **Configure logging level for another package**
Confluence: Enable debug logging
See Atlassian docs: [Configuring Logging for Confluence](https://confluence.atlassian.com/doc/configuring-logging-181535215.html)
Use **Add New Entry**
Bitbucket: Enable debug logging
See Atlassian docs: [Server debug logging for Bitbucket](https://confluence.atlassian.com/bitbucketserver/bitbucket-server-debug-logging-776640147.html#BitbucketServerdebuglogging-EnablingdebugloggingviatheUI)
You will have to do it with a PUT REST call. Using Curl:
```
curl -u -v -X PUT \
-d "" -H "Content-Type: application/json" \
/rest/api/latest/logs/logger/org.techtime/debug
```
To turn it off afterwards:
```shell
curl -u -v -X PUT \
-d "" -H "Content-Type: application/json" \
/rest/api/latest/logs/logger/org.techtime/info
```
Bamboo: Enable Debug logging
See Atlassian docs: [Logging in Bamboo](https://confluence.atlassian.com/bamboo/logging-in-bamboo-289277239.html)
Use **Add a class to log4j**
Fisheye / Crucible
Atlassian docs: [Enabling additional logging in FishEye/Crucible](https://confluence.atlassian.com/fishkb/enabling-additional-logging-in-fisheye-crucible-740000165.html)
Just enable server-wide debugging
## Re-test EasySSO
Log out of the application and close your browser or use an Incognito/In-Private browsing.
Using the same browser, navigate to your Atlassian application which has your EasySSO Add-on. If EasySSO is working correctly, you will automatically be logged in. If EasySSO is not working correctly, login as admin and proceed to the following section 'Retrieving the logs'. To bypass NTLM/Kerberos SSO append ?anon=1&logout=1 to the URL. To bypass SAML SSO append ?stopsso=1 to the URL.
## Retrieve the logs
Navigate to the EasySSO Admin screen via Administration > Add-ons > TECHTIME ADD-ONS/EasySSO and click on the 'Troubleshooting' button
See the below table to determine which log files need to be downloaded and sent to [support@techtime.co.nz.](mailto:support@techtime.co.nz) Download the log files listed in the table below based on your application. Ignore the "rotated" log files with number of date suffixes e.g. "atlassian-jira.log.1".
> ℹ️ IOPLEX Jespa log file is usually called "jespa.log" but it is possible to have it renamed in EasySSO Advanced Configuration screen. If you don't see "jespa.log" please review your settings in Administration > Add-ons > TECHTIME ADD-ONS/EasySSO > Advanced Configuration
| Application Name | Required Log Files |
| --- | --- |
| Confluence | atlassian-confluence.log
jespa.log |
| Jira | atlassian-jira.log
jespa.log |
| Bitbucket | atlassian-bitbucket.log
jespa.log |
| Bamboo | atlassian-bamboo.log
jespa.log |
| Fisheye / Crucible | atlassian-fecru.log
jespa.log |
## Restore original settings
You should revert any changes you made in steps 2 and 3 to the original settings