IdP unable to resolve principal connector

[Nate Klingenstein]

You should just need a properly defined Direct PrincipalConnector in attribute-resolver.xml(at the right point in the file):

https://wiki.shibboleth.net/confluence/display/SHIB2/DirectPrincipalConnector

Something like:

<resolver:PrincipalConnector xsi:type="Direct" xmlns="urn:mace:shibboleth:2.0:resolver:pc" 
id="ePPNPrincipalMapper" nameIDFormat="urn:oid:1.3.6.1.4.1.5923.1.1.1.6" /> 

On Nov 23, 2013, at 6:50 AM, "milton j.k.s. (jksm1g10)" <jksm1g10 at ecs.soton.ac.uk>
 wrote:

> I’m attempting to set up a shibboleth IdP to accept attribute queries from a service provider. The service provider is using the eppn as the NameID in the SAML request, however the IdP is unable to resolve a principal connector for this format. The error is:
> 
> 12:40:00.859 - DEBUG [edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:201] - Resolving principal name from name identifier of format: urn:oid:1.3.6.1.4.1.5923.1.1.1.6
> 12:40:00.860 - WARN [edu.internet2.middleware.shibboleth.idp.profile.saml2.AbstractSAML2ProfileHandler:555] - Error resolving principal name for SAML request '_b8b954956777e2a6395e0a433d799b18' from relying party 'https://kanga-gdp19-2013.ecs.soton.ac.uk/shibboleth'. Cause: No principal connector available to resolve a subject name with format urn:oid:1.3.6.1.4.1.5923.1.1.1.6 for relying party https://kanga-gdp19-2013.ecs.soton.ac.uk/shibboleth
> 
> Does anyone know how to set up a principal connector to resolve this?
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net