Single Sign-on
This guide explains how to configure Single Sign-On (SSO) between Microsoft Entra ID (Azure AD) and Incident Tracker.
On this page
Prerequisites#
- Admin access to Microsoft Entra ID (Azure AD)
- Admin access to Incident Tracker
- Permission to create and manage enterprise app registrations
Configure Single Sign-On (SSO)#
1. Register an Enterprise Application#
- Go to Microsoft Entra Admin Center > Enterprise Applications
- Click + New application > Choose Create your own application
- Name it:
Incident Tracker SSO
2. Set Up SAML SSO#
- In the app, go to Single sign-on > Choose SAML
- Enter values from Incident Tracker:
- Identifier (Entity ID)
Incident-Tracker-SSO
- Reply URL (Assertion Consumer Service URL) β add both URLs for your region
- Cloud (US):
https://secure.incident-tracker.com/(default URL) andhttps://secure2.incident-tracker.com/ - Cloud (UK):
https://secure.incident-tracker.co.uk/andhttps://secure2.incident-tracker.co.uk/ - Cloud (Canada):
https://canada.incident-tracker.com/andhttps://canada2.incident-tracker.com/
- Cloud (US):
- Sign-on URL (optional)
- The same address you use to sign in to Incident Tracker, followed by your Client ID or client name β for example,
https://secure.incident-tracker.com/[clientID or clientName]
- The same address you use to sign in to Incident Tracker, followed by your Client ID or client name β for example,
- Identifier (Entity ID)
- In the SAML Certificates section, download the Certificate (Base64)
Use the URLs for the region your Incident Tracker site is hosted in.
3. Configure SSO in Incident Tracker#
- In Incident Tracker admin settings, paste in the following:
- Login URL (SAML endpoint URL in Incident Tracker)
- Application ID
- Base64 Certificate
4. Assign Users and Test#
- Assign users/groups in Entra ID to the application
- Log in via Incident Tracker to test
βΆοΈ Interactive Tutorial β SSO Configuration#
Walks through registering the enterprise application, setting up SAML SSO, and configuring SSO in Incident Tracker.
SSO Error Codes#
After SAML is enabled, sign-in errors will appear as a code in the browser URL. Use the table below to identify and troubleshoot the issue.
| Error Code | Meaning |
|---|---|
samlfailed=error4 |
The username from the SAML response was not found in Incident Tracker, or the account has not been configured for third-party SSO login. |
samlfailed=error3 |
The SAML response was not valid. This is typically a technical issue with the SAML token or certificate configuration. |
code=6 |
A cookie or session error occurred. This may indicate an expired session, blocked cookies, or a browser configuration issue. |