Skip to main content

Troubleshooting SSO authentication

A guide to assist you in troubleshooting SSO authentication errors

If your company has set up Single Sign-On (SSO) authentication, you'll be required to log in using your personal details. When you begin the login process, you will encounter the following screen.

Provided that your credentials (email and password) are correct, you will receive immediate access to log in.

If the authentication is unsuccessful, you are likely to see this message:

If you receive this message, please follow the troubleshooting tips provided below to navigate the SSO authentication process successfully. If you are confused about the error message or troubleshooting tips, consider contacting your IT team to ensure that your credentials and information are set up correctly.

Missing Detail Errors

If you see the error “The SAML Response did not contain expected attributes”, it probably means that you are missing information on your user profile.

To fix this issue, follow these steps.

  1. Log into your user account portal (for instance, Microsoft or Okta)

  2. Check that your first name, last name, and email address are all set and correct.

If this doesn’t fix the issue you may need to configure how your data maps to Nuvo’s data. To do this, please ask your IT team to configure the following attribute statements:

  1. givenname

  2. name

  3. emailaddress

  4. surname

  5. Unique User ID

How to Fix Errors from Incorrectly Linked Attributes

When you log in via SSO, your IdP sends back a response that includes something called AttributeStatements. These are pieces of information or 'attributes' about you, each tagged with a Name property as defined by your IdP. If your SP is looking for a specific Name tag that's different from what your IdP has provided, you'll see a Missing Attribute Error. Remember, the exact wording or 'case' of these names matters a lot.

For instance, imagine your SP needs information like your ID, email, first name, and last name. We will explore how to accurately set up and connect these in systems like Azure AD. Although configurations for Okta or Google Workspaces are also possible, our example will focus on Azure.

Azure AD

In Azure AD, you can configure Attribute Statements for givenname, surname, emailaddress, and objectidentifier. You'll need to ensure that the claims are configured according to the defined mapping.

Correcting Errors from Missing Information

Sometimes, the error about missing attributes comes from certain information not being present in the user's profile. When this happens, you need to make sure the user's profile is updated to have all the necessary information.

Take, for example, how Azure always links the last name to a 'surname' claim. If you look at the Azure user profile in the example below and notice the last name is missing, this could be why you're seeing an error about missing attributes. If the Service Provider requires a 'surname' attribute and it's missing, adding this missing detail can solve the problem.

Errors about missing attributes often happen if there's a mismatch or if some information is missing between your identity provider (where your login details are stored) and the service you're trying to access. It's important for the services you use to regularly update their settings to match with your identity provider, which helps avoid these kinds of errors.


If you need any more help with SSO authentication, feel free to reach out to Nuvo's Support team at support@nuvo.credit. We're here to help!

Did this answer your question?