Specified AssertionConsumerService Location as Relative Url

Peter Schober peter.schober at univie.ac.at
Mon Jun 29 06:43:03 EDT 2015


* Surinaidu Majji <pioneer.suri at gmail.com> [2015-06-29 07:24]:
> From the above in (i), We have given absoluteUrl when sending saml
> request but in metadata "Location" is "/SSOServiceProvider/SSO"
> which is relative.

Relative to where, I wonder. Seems to me doing that doesn't provide
any security about where the protocol message (with attributes etc.)
is going. Which is the point of having metadata for the SP.

> a) Since the context (http(s)://ipaddress:port) is dynamic, How to
> make the application work by specifying "relativeUrl"
> (/SSOServiceProvider/SSO) in SP metadata?

Configure the SP to sign authn requests and configiure the IDP to
ignore ACS URL checks for (correctly) signed authn requests.
-peter


More information about the users mailing list