SAML message intended destination endpoint 'http://MY_HOST/idp/profile/SAML2/POST/SSO' did not match the recipient endpoint 'http://127.0.0.1:8080/idp/profile/SAML2/POST/SSO'

[eln00b]

Of course - as soon as I ask I fix it.
I forgot to add the *proxy_set_header* configuration in my nginx
configuration.

Now I just need to fix what seems to be the final issue:

WARN
[net.shibboleth.idp.saml.profile.impl.PopulateBindingAndEndpointContexts:410]
- Profile Action PopulateBindingAndEndpointContexts: Unable to resolve
outbound message endpoint for relying party 'my-sample-sp':
EndpointCriterion
[type={urn:oasis:names:tc:SAML:2.0:metadata}AssertionConsumerService,
Binding=urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST,
Location=http://127.0.0.1:8080/saml/SSO, trusted=false]

That still wants to use 127.0.0.1.



-----

el n00b - Trying to understand technology and help create documentation online wherever I get stuck.
--
View this message in context: http://shibboleth.1660669.n2.nabble.com/SAML-message-intended-destination-endpoint-http-MY-HOST-idp-profile-SAML2-POST-SSO-did-not-match-the-tp7632302p7632304.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.