Skip to main content

Troubleshooting SSO

A guide on some common errors and misconfigured settings in Learnsters SSO.

Written by Robin Janevret

General issues/limitations

Via Learnster Studio you are able to control the necessary settings to setup and turn on/off SSO solutions. If you are responsible for doing so but don't have the right access we recommend you start with contacting your Learnster support to check with them first.

Can I use multiple connection types or more than one IdP-provider?

It is not recommended to combine different SSO solution. But if this is still something you want or need there are 2 things you need to consider:

1. Auto login must be turned off for all SSO connections for it to work

2. You will have one SSO button for each connection on your login page

This is true even if you have the same IdP in both cases (like using OpenID and SAML). You will have to have one button per connection either way.

OpenID Connect

Info coming soon!

SAML SSO

Q: I receive the following error message "Audience Restrictions conditions not satisfied! (Local entity ID =client ID)" - what should I do?

A: This is solved by adding prefix spn: before the application ID in the SAML configuration in Learnster.

JWT based authentication

Info coming soon!

Learner-facing login issues

A learner receives an SSO error message and cannot log in

Q: A learner is getting an SSO error message when trying to log in. What should I check?

Start by identifying whether the issue affects one learner or multiple. This helps determine whether the root cause is a configuration problem or a user-specific issue.

If multiple learners are affected:

  1. Check your SSO configuration in Studio under Settings > SSO. Confirm the connection is active and the correct IdP is selected.

  2. Verify that the IdP (e.g. Azure AD, Okta, Google Workspace) has not had recent changes to the application configuration, certificates, or assigned users.

  3. Check whether Auto login is inadvertently enabled — if Auto login is on and the SSO connection is broken, all learners will be locked out. Disable Auto login temporarily to restore access while you investigate.

  4. Contact Learnster support with the exact error message and the name of your IdP.

If only one learner is affected:

  1. Confirm the learner is assigned to the Learnster application in your IdP.

  2. Check that the learner's email address in Learnster matches exactly what the IdP sends in the SSO assertion (case-sensitive).

  3. Ask the learner to clear their browser cookies and cache, then try again.

  4. If the learner uses the Learnster U mobile app, note that SAML SSO is not supported on iOS or Android — they must use OpenID Connect (OIDC). See the article Important info before using Learnster U (iOS and Android app) for details.

  5. If the issue persists, have the learner try logging in via the direct URL (not the SSO button) to rule out a browser redirect issue.

A learner has a duplicate account or cannot log in after an email change

Q: A learner is blocked from logging in because of a duplicate account or an email conflict. How do I resolve this?

This typically happens when a user previously existed in Learnster with the same email, was soft-deleted, and then a new account was created (or an SSO provisioning event triggered a new record) using the same email.

To resolve a duplicate account:

  1. In Studio, search for the learner by email — include inactive/deactivated users in the search.

  2. If a soft-deleted user exists with the same email, reactivate that account instead of creating a new one. Reactivating restores the learner's existing course history.

  3. If two active accounts exist for the same learner, merge or deactivate the duplicate. Contact Learnster support if you cannot resolve the conflict from the Studio interface.

  4. If you are using SCIM provisioning, check that your IdP is not creating new user records on re-hire or role changes. Configure your SCIM setup to match on email and reactivate existing records rather than creating duplicates.

If you see the error "A user with this email address already exists" when trying to update a learner's email, see the article How can I fix the error when trying to change an employee's email that says 'A user with email address already exists'? for the resolution steps.

Did this answer your question?