Specified AssertionConsumerService Location as Relative Url

[Surinaidu Majji]

We have upgraded from IDP-2.4 to 3.1. We have prepared our own Service
Provider which sends SAML request to Shibboleth IDP.
So we have prepared the SP metadata which will be useful while
communicating with IDP.Here We are telling to IDP about "*consumerUrl*" in
two places.

i) when sending SAML request (IDP-2.4 & IDP-3.1)
 consumerUrl = http(s)://ipaddress:port/SSOServiceProvider/SSO
 authnRequest = this.buildAuthnRequestObject(spUrl, consumerUrl);


ii) In SP-metadata
in IDP-2.4 & IDP-3.1
<md:AssertionConsumerService Location="/SSOServiceProvider/SSO" index="1"
isDefault="true"
      Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"/>


>From the above in (i), We have given absoluteUrl when sending saml request
but in metadata "Location" is  "/SSOServiceProvider/SSO" which is relative.
The above has been worked somehow in 2.4 but it is not working 3.1. We are
getting the following log messge while running the IDP.

 "The consumer urls did not match"

*Queries:*

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


b) Can we use any other index (ex: index=0) to specify
 "AssertionConsumerService" in point(i)? like below.

  <md:AssertionConsumerService Location="/SSOServiceProvider/SSO" index="0"
isDefault="true"
      Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"/>


Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150629/181d8cac/attachment.html>