Hey there, I'm encountering a challenge with SAML SSO POST binding in the context of a protected Web application that includes Ajax script. Following the initial authentication process, which is managed by the browser, the Ajax code within the Web application successfully retrieves data from the server. However, issues arise when the security session expires and the service provider (SP) sends a SAMLRequest back to the identity provider (IdP) via SAML SSO POST using a form with auto submit. As the response returns with a code 200, the form containing the SAMLRequest ends up triggering an unexpected Ajax callback that isn't equipped to handle it.
So, here's my query:
Is there a method for the Ajax callback code to communicate to the browser that it should refrain from processing this particular response and let the browser manage it conventionally?
If not, how can I replicate the behavior of the browser, which simply submits the pre-filled form automatically?
Thank you, Gang