Sending SAML response to a different URL

Yoav Cohen 1 Reputation point
2020-11-05T09:30:38.78+00:00

Hello,

We are trying to establish SSO from Azure AD to an application, with a proxy in the middle. Assume the application URL is: example.app.com and the proxy URL is example.proxy.com. We would like Azure AD to send the SAML Response to example.proxy.net instead of sending it to example.app.com.

We were able to make this setup work in Okta, by setting the following values on our SAML 2.0 application:
Single sign on URL: https://example.proxy.net/login
Recipient URL: https://example.app.com/login
Destination URL: https://example.app.com/login
Audience URI (SP Entity ID): https://example.app.com/login

As you can see, we override the Single sign on URL with the proxy URL and then have to explicitly set the rest of the URL in order for the SAML assertion to be accepted by the application. In Okta, the description of the Single sign-on field says: The location where the SAML assertion is sent with a HTTP POST. This is often referred to as the SAML Assertion Consumer Service (ACS) URL for your application.

We are trying to recreate the same setup in Azure AD using an Enterprise Application but we can't find the equivalent field in Azure to Okta's Single sign-on in order for Azure to send the HTTP POST to our proxy. Can you help us find that field?

Thank you,
Yoav.

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

6 answers

Sort by: Most helpful
  1. Manish Vishnoï 21 Reputation points
    2023-01-06T15:36:01.407+00:00

    Hi,

    We also have similar problem where we are trying to use a reverse proxy in front of our application. Our application is rejecting SAML response coming with the destination set to "Reserve Proxy URL" .

    Is this issue still there or we have a workaround ??

    Thanks !