Problem Connecting Azure AD SSO to DOMO

Ashutosh Joshi 1 Reputation point

I'm configuring AZURE AD SSO to DOMO for our origination and it showing this error from AZURE is

AADSTS750054: SAMLRequest or SAMLResponse must be present as query string parameters in HTTP request for SAML Redirect binding.
See resolution steps below.Root cause: Azure AD wasn’t able to identify the SAML request within the URL parameters in the HTTP request. This can happen if the application is not using HTTP Redirect Binding for sending the SAML request to Azure AD.Resolution:The application needs to send the SAML request encoded into the location header using HTTP Redirect Binding. For more information about how to implement this, read the section HTTP Redirect Binding in theSAML protocol specification document.If you're the admin configuring single sign-on, verify:The application supports service provider-initiated SSO and single sign-on is enabled on the application side.Verify the sign-on URL is configured. Currently, the application Domo is not sending a SAML request to Azure AD in the redirection from the application sign-in page to Azure AD sign-in page.


Checked the configurations couple of times and problem still occurring.
Let me know your thought about the issue.

Thanks and regards

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,568 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Siva-kumar-selvaraj 15,601 Reputation points

    Hello @Ashutosh Joshi ,

    Thanks for reaching out.

    It seems to be your application using incorrect HTTP binding to send SAMLP request to Azure AD for authentication.

    It should be HTTP Redirect binding as per OASIS Standard, this defines a mechanism by which SAML protocol messages can be transmitted within URL parameters as shown:


    HTTP 302 Redirection call to

    Note : If you look at above URL, you could see SAMLRequest part of URL parameter

    Alternatively, more complex message content can be sent using the HTTP POST or Artifact bindings. To learn more about HTTP Redirect binding (see Section 3.4)

    In this scenario, I would recommend you to collect HTTP trace to verify if application sending SAML request with HTTP Redirect binding by using either SAML-Tracer orfiddler Tracer so you would see trace similar to below:


    Hope this helps.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    1 person found this answer helpful.
    0 comments No comments

  2. Ashutosh Joshi 1 Reputation point


    Thanks for getting back to me so quickly. I checked with SAML-Tracker and you were right I'm not getting any "HTTP redirect binding". No SAML request can be seen in the SAML tracker during the "TEST LOGIN". Any idea how can I resolve this issue. ?