Getting PowerFAIDS NetPartner to work with Shibboleth 3

[Lipscomb, Gary]

Doesn't V3 ignore
      <NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat> 
if it's in  metadata anyway?

   idp-warn-2018-05-15.log.gz:2018-05-15 12:31:07,038 - WARN [org.opensaml.saml.common.profile.logic.MetadataNameIdentifierFormatStrategy:75] - Ignoring NameIDFormat metadata that includes the 'unspecified' format  

Regards

Gary

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Peter Schober
Sent: Wednesday, 16 May 2018 16:34
To: users at shibboleth.net
Subject: Re: Re: Getting PowerFAIDS NetPartner to work with Shibboleth 3

* Daudt, Carl <crdaudt at taylor.edu> [2018-05-15 20:17]:
> The most recent issue was fixed by changing where I specified the
> NameIDFormat, which I had in the Net Partner metadata file.
[...]
> The change that got Net Partner SSO working for was removing the
> sixth line (i.e., the <NameIDFormat> specification from the metadata
> file.  Instead, I placed the specification as a
> nameIDFormatPrecedence entry in reying-party.xml

That would be a bug effecting noone else so far.

FWIW, I only use SAML Metadata for NameID selection and it works fine
for me.
-peter
-- 
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net