SAML1

[Peter Schober]

* Arnal, Pascal <Pascal.Arnal at lacapitale.com> [2015-03-16 15:07]:
> I can't get SAML 1 assertion in my SP with logs :
> 
> Log of the SP :
> 2015-03-16 09:57:49 ERROR Shibboleth.AttributeResolver.Query [4]: exception during SAML query to https://IDP_URL:8443/idp/profile/SAML1/SOAP/AttributeQuery: CURLSOAPTransport failed while contacting SOAP endpoint (https://IDP_URL:8443/idp/profile/SAML1/SOAP/AttributeQuery): Failed connect to IDP_URL:8443; Connection refused
> 2015-03-16 09:57:49 ERROR Shibboleth.AttributeResolver.Query [4]: unable to obtain a SAML response from attribute authority
> 2015-03-16 09:57:49 INFO Shibboleth.SessionCache [4]: new session created: ID (_30b2fc7d8496d63b20467ccf2fb26a14) IdP (https://IDP_URL/idp/shibboleth) Protocol(urn:oasis:names:tc:SAML:1.1:protocol) Address (xxxxxx)

OK, the query failed with "Connection refused" but why does the IDP
then log the number of attributes below? Seems those have successfully
been pushed over the browser, i.e., the SP should have these available:

> 2015-03-16 09:57:49,294 - INFO [Shibboleth-Audit.SSO:241] - 20150316T135749Z|urn:mace:shibboleth:1.0:profiles:AuthnRequest|_E24C384BDFDF7BEB364C1AAAB6F9FD79!1426514268|https://SP_URL/sp/shibboleth|http://shibboleth.net/ns/profiles/saml1/sso/browser|https://IDP_URL/idp/shibboleth|urn:oasis:names:tc:SAML:1.0:profiles:browser-post|_e58df4062eb390cce5bd7e694f9a56f3|USER_ID|urn:oasis:names:tc:SAML:1.0:am:password|SHIB_USER_UID,SHIB_USER_MAIL,SHIB_USER_GIVENNAME,SHIB_USER_MEMBER,SHIB_USER_COMPANY,SHIB_USER_DISPLAYNAME|AAdzZWNyZXQxdYIXcddaXPJZZXKROo7iKwSfAFTAgLZPE4PRW5NTm550rKdSiekmTYKcsqTotFMWxkBnt5Cj580oOEhAfuabFvgMZK6EIqHBSLFPmOlEAvanq/Vg9uJjXf4d0IINqNiRAAOHVVgzD1cSKXb1q71PIvuGtlGZ1w/c4mXCPAk=|_d6aa8474d8316cd3b15653c793242dd3

Though the custom attribute IDs ("SHIB_USER_UID") in the IDP hint at
possible custom attribute names on the wire, which would mean that
none of these attributes would show up on the SP unless such entries
were added to its attribute-map.xml?
-peter