If a user sees a Microsoft error when signing in to Symbiant with single sign-on, find the error code below.
Tip: The most common single sign-on problem isn’t an error code at all: it’s the user’s email address in Symbiant not matching the case in your directory. See Enabling SAML for Users in Symbiant.
AADSTS50105: User Not Assigned #
The message: AADSTS50105: The signed in user is not assigned to a role for the application.
Why it happens: The user hasn’t been given access to the Symbiant app in Microsoft Entra ID (Azure AD).
How to fix it: Assign the user to the app, or add them to a group that is assigned to it. In the app, go to Users and groups > Add user/group. Microsoft’s guide: Assign users and groups to an application.
AADSTS50003: No Signing Key Configured #
The message: AADSTS50003 when trying to sign in.
Why it happens: The signing certificate Symbiant Support has doesn’t match the one in your app, or isn’t recognised.
How to fix it: Create a new certificate and send it to us.
- In the app’s Single sign-on page, under SAML Signing Certificate, click Create new certificate.
- Choose an expiry date and click Save.
- Tick Make new certificate active, click Save at the top of the page, and accept the rollover.
- Remove the old, unused certificate.
- Send the new certificate to Symbiant Support in a support ticket.
AADSTS650056: Misconfigured Application #
The message: AADSTS650056: Misconfigured application.
Why it happens: The Issuer that Symbiant sends doesn’t match the Identifier (Entity ID) set in your app.
How to fix it: In the app’s Basic SAML Configuration, check the Identifier (Entity ID) matches exactly the value Symbiant Support gave you. See Setting up SAML SSO with Azure.
