Troubleshooting SSO Login Issues

Follow

At Swiftly, we support Single Sign-On (SSO) for organizations that integrate authentication through Microsoft Entra (formerly Azure AD). While SSO provides seamless access, it can occasionally lead to login issues.

This article outlines common SSO errors and provides next steps for troubleshooting, and explains when to escalate the issue to your IT department or the Swiftly Support team.

⚠️ Important: This guide applies only to customers logging in via SSO. If you use a regular email/password login to access Swiftly, these steps do not apply.


SSO Login Issues

1. Access Denied by Microsoft Entra

  • Symptom: You see an error indicating your account doesn’t have access to Swiftly.
  • Cause: Your Microsoft Entra administrator hasn't assigned your account access to the Swiftly application.
  • Fix: Ask your IT team to:
    • Confirm your account is part of the correct group or has direct assignment to the Swiftly enterprise application in Entra.
    • Ensure that no conditional access policies are blocking sign-in.

sso_image1.png

Once access is granted access in Microsoft Entra, access will be restored successfully.

2. Uncommon Login Errors (e.g., Credential Mismatch, RequestedAuthnContext)

Symptoms:

  • Login error without clear explanation.
  • Errors referencing "RequestedAuthnContext" or “credential mismatch”.

🚫 Users: These errors are not fixable through browser settings or personal account changes.

👉 Please contact your IT administrator and share a screenshot of the error.

sso_2.png Screenshot 2025-04-11 at 1.04.25 PM.png

🛠️ For IT Administrators

Fix:

These errors often stem from Microsoft Entra configuration issues.

To troubleshoot, please visit: https://learn.microsoft.com/en-us/troubleshoot/entra/entra-id/welcome-entra-id

Please contact Swiftly at support@goswift.ly if:

  • All IT-side configurations are confirmed correct but login still fails.
  • You need Swiftly to verify SSO logs or help coordinate with your IT team.
  • When submitting a ticket, include:
    • Affected user’s email address.
    • Screenshot or copy of the error message.
    • Confirmation that the user has been assigned access in Microsoft Entra.

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.