Merge pull request #290 from silversword411/main

SSO Troubleshooting section
amidaware · Nov 25, 2024 · 8f159a8 · 8f159a8
2 parents f066e6e + 4ff21ea
commit 8f159a8
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 2 deletions.
diff --git a/docs/ee/sso/images/entra_error_loggingin.png b/docs/ee/sso/images/entra_error_loggingin.png
diff --git a/docs/ee/sso/sso.md b/docs/ee/sso/sso.md
@@ -350,7 +350,6 @@ For those who have no interest in using this feature and want it completely disa
     === ":material-docker: Docker install"
 		Add `TRMM_DISABLE_SSO=True` to your `.env` file and run ```docker compose down && docker compose up -d ```
 
-
 ## How do I activate SSO as a new sponsor?
 
 *Ignore the following if you're an existing sponsor upgrading from a version below 0.20.0, as SSO will automatically be activated for you during the upgrade process.*
@@ -379,4 +378,15 @@ For those who have no interest in using this feature and want it completely disa
 		docker compose up -d
 		```
 
-For any issues with activating SSO, [open a ticket](https://support.amidaware.com).
+For any issues with activating SSO, [open a ticket](https://support.amidaware.com).
+
+## Troubleshooting
+
+!!!note
+	SSO errors are usually logged on your providers side. Check there for error messages.
+
+"There was an error logging into your provider."
+
+![Error logging into your provider](images/entra_error_loggingin.png)
+
+The email address exists in the TRMM local users as well as your SSO. Update the local TRMM users email to [email protected] and then you'll be able to login.