Error resolving principal name

[Peter Schober]

* Morris, Andi <amorris at cardiffmet.ac.uk> [2015-02-26 14:29]:
> 20:33:56.393 - WARN
> [edu.internet2.middleware.shibboleth.idp.profile.saml1.AbstractSAML1ProfileHandler:568] - Error resolving principal name for SAML request from relying party 'https://academic.mintel.com/shibboleth'. Cause: No information associated with transient identifier: _15c9b9b5bd0c3aa11d088549e802a3dd

Note that this SP speaks SAML2 just fine (I just tried to log at
http://academic.mintel.com/ via "Federated Log In"), so there should
be no reason to use (a) use SAML1, and (b) attribute queries.

While that's no explanation why the attribute query failed (which a
Shib IDP supports by default once you have set up the SOAP port
correctly, which seems to be the case here) you might still prefer to
remove the reason this happens in the first place.

Then you can still try to find out whether your IDP works with
Attribute Queries (potentially involving an SP of your own, or one
provided by someone else, e.g. the UKfederation or TestShib) or
whether you'd like to continue supporting queries in the first place.

E.g. if all you ever send to such SAML1 SPs is an eduPersonAffiliation
and/or the common-lib-terms eduPersonEntitlement attribute value you
might consider pushing those attributes over the browser, unencrypted.
Then most SPs won't see a need to issue an attribute query, not even
via SAML1.
-peter