Documentation / Answers / Troubleshoot single sign-on

Troubleshoot single sign-on

Last reviewed 2026-11-16.

Short answer. Microsoft sign-in shows AADSTS50105 when that person is not assigned to the Entra application. Entra's Test button, used before Enable SSO is on, gets "SSO not configured for organization" followed by the organization id. Identifier (Entity ID) and Reply URL have to be the SP Entity ID and the ACS URL copied from Single Sign-On. Paste Certificate (Base64), including the BEGIN and END lines, into IdP X.509 Certificate, and paste Microsoft Entra Identifier into IdP Entity ID. An email domain that is not under Allowed email domains is refused with "Email domain" and the domain, then "is not allowed for SSO."

Setup is Set up single sign-on. The page title is Single Sign-On (SSO).

AADSTS50105

What you see. Microsoft's sign-in page shows AADSTS50105.

Why. That person is not assigned to the Entra application. Meridian does not show this code. Entra does, when the application requires assignment and the account is not on it.

How to fix. In Microsoft Entra, open the Onaro Meridian enterprise application and assign the person, or a group they are in. Then have them sign in again.

SSO not configured

What you see. Entra's Test shows "SSO not configured for organization" and then the organization id.

Why. Test sends the sign-in to the reply URL before Enable SSO is on. A new configuration is saved with SSO off. Meridian answers that reply URL only after SSO is enabled, so the test is refused with that sentence.

How to fix. On Single Sign-On (SSO), turn on Enable SSO and save. Run Test in Entra after that.

Identifier or Reply URL does not match

What you see. Microsoft reports that the identifier or the reply URL does not match.

Why. Identifier (Entity ID) or Reply URL in Entra is not the value on this organization's SSO page.

How to fix. On Single Sign-On (SSO), copy SP Entity ID into Entra's Identifier (Entity ID). Copy ACS URL (Reply URL) into Entra's Reply URL. Use the Copy button on each value. Save in Entra, then test again.

Which certificate

What you see. Sign-in fails after the certificate step, or the certificate on the SSO page is not the one Entra is using.

Why. Entra offers more than one certificate download. Meridian's field is IdP X.509 Certificate. The matching download in Entra is Certificate (Base64).

How to fix. In Entra, under SAML signing certificate, download Certificate (Base64). Paste the whole file into IdP X.509 Certificate, including the BEGIN CERTIFICATE line and the END CERTIFICATE line. Save on Single Sign-On (SSO).

IdP Entity ID

What you see. The IdP Entity ID is rejected, or sign-in does not reach your tenant.

Why. The IdP Entity ID is not Microsoft Entra Identifier. It is not the SP Entity ID.

How to fix. In Entra, under Set up Onaro Meridian, copy Microsoft Entra Identifier. Paste it into IdP Entity ID. It looks like https://sts.windows.net/<tenant-id>/. The SP Entity ID stays in Entra's Identifier (Entity ID), as in the mismatch entry above.

Email domain is not allowed

What you see. Sign-in stops with "Email domain {domain} is not allowed for SSO." The {domain} is the part of the address after @.

Why. That domain is not in Allowed email domains on Single Sign-On (SSO).

How to fix. Add the domain on Allowed email domains and save. Type the domain only, such as acme.com, with no @. A personal email domain is refused with "A personal email domain cannot be used for SSO." Use the company domain instead.

AADSTS75011

What you see. Microsoft's sign-in page shows AADSTS75011.

Why. The sign-in Entra received asked for a password, and that person signed in with MFA or a security key. A new sign-in from the Meridian login page does not ask Entra for a password method. Meridian leaves the method to Entra.

How to fix. Start again from the Meridian login page and choose Login with SSO. Do not retry an old Microsoft page. Leave Entra's sign-in methods as they are, including MFA and a security key.

How Entra signs the response

What you see. Sign-in stops and the message says the response is not signed.

Why. Entra's default signs the assertion and does not sign the response message. Meridian checks the assertion with the certificate in IdP X.509 Certificate. That is the signing option Meridian accepts. Sign SAML response and assertion also works.

How to fix. In the Entra enterprise application, leave SAML signing on the default, which signs the assertion. If it was changed, set it back to that default. Keep Require signed assertions on in Meridian. Do not turn on a requirement that the response message itself be signed.

The next page says 405

What you see. Right after Microsoft's Test, or right after signing in, the browser shows 405 on a Meridian page or on the site root.

Why. The sign-in reached Meridian, and the next page was opened with POST. A page on the site accepts GET.

How to fix. Sign in again from the Meridian login page. Meridian sends the browser on, and the page loads with GET. Microsoft's Test has no return address, so it opens the Meridian dashboard. A return address that is not an Onaro page is refused, and the dashboard opens instead. Do not bookmark the reply URL.