Does Okta support AssertionConsumerServiceURL as the destination for posting SAML assertion? Skip to main content
https://support.okta.com/help/answers?id=906f0000000dfknia4&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fanswers
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Ask Search:
Jay WeinsteinJay Weinstein 

Does Okta support AssertionConsumerServiceURL as the destination for posting SAML assertion?

I'm populating a custom AssertionConsumerServiceURL in the AuthnRequest sent to Okta, but the SAML assertion is being sent to the static ACS URL configured in Okta.

I tried both signed and unsigned requests, but in both cases the request is not going to my custom destination. 

Is this supported?
Scott DennyScott Denny
I am encountering the same problem. The UI seems to allow multiple URLs and indices in "Requestable SSO URLs", which presumably correspond to AssertionConsumerServiceIndex and AssertionConsumerServiceURL, but the URL POSTed to is always the "Single sign on URL". I'm not sure why those are in the UI, since they seem to do nothing. Maybe a bug. I am trying to use multiple URLs so I don't need to make an app for every single SP I have.
Michael FUERYMichael FUERY
OTKA: What's the latest on this?
Scott DennyScott Denny
FYI: I got this working by making sure my AuthnRequest was properly set up. I'm still not sure what the issue was, but it might have been that I needed to set the protocol binding to POST in my AuthnRequest. This works for me for both AssertionConsumerServiceIndex and AssertionConsumerServiceURL.