You may encounter errors when setting up Single Sign On (SSO) in your Bynder portal. If you have followed the steps to set up SSO but are still having trouble logging in, please refer to the chart below to fix the problem.
How to Troubleshoot SSO
-
Navigate to Settings > Advanced Settings > Portal Settings.
-
Click Login Configuration on the left sidebar.
-
Select the SSO method that you would like to review.
-
Select Logs.
-
Here, you will see the list of login events.
-
Click Login failed to see the specific error.
-
Use the information in the chart below to help identify and troubleshoot the issue.
These errors correspond to invalid SAML configuration in the idp and Bynder platforms.
SAML Response Validation|
Error |
Description |
|---|---|
|
SSO disabled |
This SSO method is disabled in Bynder's login configuration. |
|
Invalid issuer |
Received "{received}" instead of the expected "{expected}," which is the configured value for Identity Provider Identifier. |
|
Invalid audience |
"{Received}" was not found in the audience restriction. |
|
Invalid signature |
The signature validation of the SAML response failed. The certificates in the SAML response and the SSO method configuration don't match. |
|
Response not signed |
No signature was found in the SAML response. The signature hasn't been set up in the identity provider. |
These errors may happen specifically for Google SSO flows.
InvalidGoogleThese errors may happen specifically for OpenID SSO flows
|
Title |
Description |
|---|---|
|
SSO disabled |
This SSO method is disabled in Bynder's login configuration. |
|
Authorization endpoint |
The server denied the authorization request and may have provided more information. Error: "{error}," error description: "{error_description}." |
|
Token endpoint |
The server responded with a {status_code} status code and may have provided more information. Error: "{error}," error description: "{error_description}." |
|
JWKS endpoint |
Unable to retrieve the JSON Web Key Set from the configured JWKS URL. |
|
Invalid Token |
The token endpoint did not return a token, or the token is invalid. |
|
Userinfo endpoint |
The server responded with a {status_code} status code and may have provided more information. Error: "{error}," error description: "{error_description}." |
|
JWT |
The JWT returned by the token endpoint could not be validated against the retrieved JSON Web Key Set. |
These errors may happen in the SSO flows and are relative to user management in Bynder's platform.
|
Error |
Description |
|---|---|
|
Email not found |
No valid email was found in the attribute with the Name "{attribute}." |
|
Email not found |
No valid email was found in the NameID value. |
|
First name not found |
No value was found in the attribute with Name "{attribute}." |
|
Last name not found |
No value was found in the attribute with Name "{attribute}." |
|
Inactive user |
This user is currently deactivated and not allowed to log in. |
|
User not found |
The user does not exist and couldn't be created because, just in time, user provisioning is disabled in the SSO method configuration. |
|
Missing username |
No valid username was found in the attribute with the Name "{attribute}." |
|
Not enough seats |
Users could not be created because the maximum number of user seats for this type has been reached. |
If you are still having issues please contact Customer Support.
Updated