Having issues getting your SSO setup to work with SimplyPrint? Worry not! The solution is most likely found in this guide!

Prerequisite: is the SSO setup done correctly?

It's always good to start by answering the question; "Is everything correct setup-wise?".

You can find our SSO setup guides here:

• Google Workspace SSO setup: Set up Google Workspace Single sign-on (SSO) for SimplyPrint
• Microsoft Entra ID setup: Setting up SAML Single Sign-On (SSO) with Microsoft Entra ID for SimplyPrint
• Other / generic SAML SSO setup: Set up Single sign-on (SSO) for SimplyPrint

Type 1: your SSO idP refuses to send you to SimplyPrint

If we redirect you to your identity provider (idP), but after login the idP does not send you back to SimplyPrint, it may be that there's a settings-mismatch.

Check that the Entity ID for SimplyPrint as well as the Return URL/Callback/ACS URL is correct; go to the SSO settings in SimplyPrint and verify that the value you can copy here, is the value that is present in your idP SSO application settings for SimplyPrint.

If it continues to fail, there may be a problem with your idP: if they don't show a specific error message that you can use, reach out to your idP or our support.

Type 2: missing attributes, e.g.: "first_name is required"

A common issue with SSO setups are missing attributes: this is when SimplyPrint expects, and requires some data, that we do not get. There can be 2 reasons for us giving you this error;

1. We don't get the data from the idP at all: missing attribute
2. Attribute name mismatch

There are a couple of common cases of this;

Attribute name mismatch: attribute has another name than the one provided to SimplyPrint

How SAML SSO works in terms of attribute naming can, unfortunately, vary from idP to idP: some let you define your own attribute names, while some let you define something, like an ID, but where it's unclear that this is not actually what it sends to platforms like ours as the attribute name.

You may have entered "email" as the attribute name in SimplyPrint, while your idP actually sends us a long string like "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress".

In Microsoft Entra, the "ID" of the attribute is not the name that we receive, and the name you see, like "email", is not the whole attribute that we receive either; we receive [namespace]/[name], so "email" becomes "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/email" - now, this particular case (if you enter "email" in SimplyPrint, but they prefix it with something like "://schemas.xmlsoap.org/ws/2005/05/identity/claims/"), we handle gracefully by finding/accepting the attribute name anyway.

Missing attributes

If it's not just a name mismatch - them calling it one thing, us expecting another and thereby not being able to find ("map") it - it may be that the attribute is actually missing and is not sent to our platform upon successful SSO login.

This commonly happens if the value is empty. For example; you may provide us with "email", and the name is correct in both idP and SimplyPrint - but the user actually doesn't have an "email" value.

This is a common issue with Microsoft Entra ID, where the email of the user was actually the ID and not the "email" field - resulting in it being empty, which results in it not being present in the SAML attribute list.

Another common empty value is "first name" and "last name", if your idP only has a "name" field, with both first- and last name. This is why you only need to provide us one; either the Full name, or First AND last name.

Troubleshooting attributes

In the SimplyPrint web panel, in the SSO setup settings (https://simplyprint.io/panel/settings/organization#registration), down by the "Attribute mapping" you will find a section called "Last received attributes (debug)". This will show if there has been a successful attempt at logging in with SSO for your account, and will show the last received attributes; names and values for troubleshooting purposes.

If the "Last received attributes" section does not show, that means we either haven't received any, or what we received was an empty response - but rule of thumb; if your idP approved your login and sent you back to SimplyPrint after login, we will have received something.

If you see the "Last received" section, you can use this to check what the attribute names are and change your mapping accordingly.

Lastly, your idP may have a debugger as well, which can give you some of the same data.

We hope this article helped you solve your SSO issues. If not; feel free to reach out to our support.

Updated on: 12/09/2025