title: SAML 2.0: How to configure Assertion Consumer Service URL
body: <p>I am implementing a SAML 2.0 Service Provider which uses Okta as the Identity Provider. I would like to configure the Assertion Consumer Service (ACS) URL so that the SAML 2.0 from my Service Provider app is reflected back in the assertion.</p>
  
  <p>However, I am noticing that the Okta Identity Provider instead sends the SSO Endpoint configured in the Okta configuration and ignores the ACS that was actually sent. Also, I get an error perhaps the ACS from SP doesn't match the meta-data there.</p>
  
  <p>If ACS URL is not the right way to send a short ID to IDP for it to reflect back in the assertion, what other mechanism can be used for this purpose.</p>
  
  <p>Example:</p>
  
  <p>The SAML 2.0 SAMLRequest sent by the SP app is:</p>
  
  <p>assertion_consumer_service_url:
  https: //host.com:port/saml/consume? entityId=N&amp;myName=username</p>
  
  <p>The configuration on Identity Provider has the meta-data:</p>
  
  <p>Single Sign-on URL:
  https: //host.com:port/saml/consume?entityId=N</p>
  
  <p>Note that the myName changes from one request to the next, as it is our way of verifying that the response has name_id which matches the original username being sent.</p>
  
  <p>Also, if there is a way for the Service Provider to let the Identity Provider assert that an SP-managed name (such as username), that would be fine for our needs. How does one specify this?</p>
  
  <p>Thanks</p>