<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D50Z00008G7UkfSAFOkta Classic EngineOkta Integration NetworkAnswered2024-04-17T09:04:21.000Z2017-04-17T14:16:53.000Z2020-12-19T15:56:42.000Z
  • DerrickC.87188 (Customer)

    I figured out the reason:  StreamWriter was adding a zero-width Byte Order Mark to the start of the XML before base64 encoding, and Okta couldn't interpret the resulting XML auth request. (Thanks, James.)
  • r1y9k (r1y9k)

    I have the same problem. SAML client - mod_auth_mellon.

    I am able to catch saml request with saml tracer, but it does not give me idea what is going wrong. Also there is nothing useful in the logs, available via partner okta dashboard. What else can be done to debug this issue?
  • tzpk9 (tzpk9)

    I'm developing a Qt Application using QtWebKit and I'm seeing this Bad SAML Request 400. What are my options at this point? I haven't seen any SAML tracer or browser extension options for this.

     

    My QwebView steps are the following:

     

    1. Decode Base64 samlRequest
    2. Use decoded result in QWebView::setHtml( ) If it is a POST and QWebView::load(url) if it is REDIRECT
    3. I only see the Bad Request Error Page on a POST
    Expand Post
    • bo9oo (bo9oo)

      We ran into something similar when authenticating our Qt app against Google SSO. The problem was that the login code Google returns is URL-encoded, and needs to be decoded before being exchanged for an access token. See the reference to setModifyParametersFunction in the linked post.

  • KushS.68510 (Customer)

    I get "400 Bad Request. Your request resulted in an error. Description: Bad SAML request" its happening after correct credentials ,

     

    how to resolve ?

This question is closed.
Loading
400 Bad SAML request?