Articulate 360 Teams: Common Single Sign-On (SSO) Issues
Article Last Updated
This article applies to:
Is your Articulate 360 team having trouble with our single sign-on (SSO) solution?
To get you and your team on track quickly, we compiled a list of some of the most common causes of SSO issues and how to fix them. If you need extra support at any point, contact us at enterprise@articulate.com. We're happy to help!
For more details about SSO setup, visit our main support article.
|
Issue |
Solution |
|
There's a problem with the configured user values. |
Articulate 360 receives claims and attributes that supply details about the user from the identity provider (IdP). For SSO configuration, you only need to provide the following SAML values: Subject We support the email address format, which must match the user's email address in the IdP. Attributes
Double-check that the values you provided for each are valid and correctly formatted. Values are case-sensitive. Incorrect, missing, or additional values can result in duplicate usernames or other errors when users try to sign on to the desktop app via the organization's IdP. |
|
The public IdP certificate used to validate SAML assertions is incorrect or expired. |
You must maintain a correct and active public IdP certificate. If it's incorrect or expired, email the up-to-date certificate to enterprise@articulate.com. |
|
The user needs to accept your invitation to join your team, or they signed in with a different Articulate ID. |
In the team management console, double-check the status of the invitation you sent to the user. Their status should be a green circle with a check mark. If it isn't, ask the user to accept your invitation by signing in directly to https://id.articulate.com/redirect/account using the email address you used to invite them. |
|
The user's Articulate 360 desktop app needs to be updated. |
The minimum Articulate 360 desktop app version required is 1.49.24347.0. Earlier versions of the desktop app prompt users to enter their login credentials instead of signing in via the organization's IdP. If users are running earlier versions, they'll need to uninstall their desktop app and install either the minimum or latest version. They only need to update the Articulate 360 desktop app to solve the SSO problem, but we recommend updating authoring apps as well. That way, they'll benefit from the security enhancements, new features, and bug fixes in the latest versions of Storyline 360, Studio 360, Replay 360, and Peek 360. If you centrally manage app installations for your organization, use the enterprise deployment guide and MSI files to install the Articulate 360 desktop app on the user's computer. |
|
The default destination for the Relay State is the Account Management Console (https://id.articulate.com/redirect/account). |
Articulate 360's Relay State directs users to their Account Management Console (https://id.articulate.com/redirect/account) by default. However, you can change where users land after they sign in with SSO. For example, your team might prefer direct access to Articulate 360 authoring apps after they sign in. In that case, configure the Relay State to the Articulate 360 dashboard (https://id.articulate.com/redirect/360). |