Nameid unspecified with Legacy Relying party
Ramaiah, Vanna G.
ramaiah at musc.edu
Mon Mar 20 19:38:58 EDT 2017
I upgraded from v2.4 to v3.3. Everything seems to be working fine except for "unspecified" nameids. I am using Legacy Relyingparty configuration. I didn't change anything much in relying party from V2 upgrade except for commenting out Metadata provider and security trust engines.
How to solve the nameids unspeficied problem. While I contact the SPs to change the nameids format specified, I am afraid that cannot happen soon.
In idp-properties.log, it is ignoring the unspecified format and making that as transient.
2017-03-20 19:12:00,249 - DEBUG [org.opensaml.saml.common.profile.logic.AbstractNameIDPolicyPredicate:218] - Policy checking disabled for NameIDPolicy with Format urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified
2017-03-20 19:12:00,249 - WARN [org.opensaml.saml.common.profile.logic.MetadataNameIdentifierFormatStrategy:75] - Ignoring NameIDFormat metadata that includes the 'unspecified' format
2017-03-20 19:12:00,249 - DEBUG [org.opensaml.saml.saml2.profile.impl.AddNameIDToSubjects:323] - Profile Action AddNameIDToSubjects: Candidate NameID formats: [urn:oasis:names:tc:SAML:2.0:nameid-format:transient]
In services.properties :
idp.service.relyingparty.resources= shibboleth.LegacyRelyingPartyResolverResources
In saml-nameid.properties:
idp.nameid.saml2.legacyGenerator= shibboleth.LegacySAML2NameIDGenerator
idp.nameid.saml1.legacyGenerator= shibboleth.LegacySAML1NameIdentifierGenerator
Here is relying-party sample.
<rp:RelyingPartyGroup xmlns:rp="urn:mace:shibboleth:2.0:relying-party"
xmlns:saml="urn:mace:shibboleth:2.0:relying-party:saml" xmlns:metadata="urn:mace:shibboleth:2.0:metadata"
xmlns:resource="urn:mace:shibboleth:2.0:resource" xmlns:security="urn:mace:shibboleth:2.0:security"
xmlns:samlsec="urn:mace:shibboleth:2.0:security:saml" xmlns:samlmd="urn:oasis:names:tc:SAML:2.0:metadata"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:mace:shibboleth:2.0:relying-party classpath:/schema/shibboleth-2.0-relying-party.xsd
urn:mace:shibboleth:2.0:relying-party:saml classpath:/schema/shibboleth-2.0-relying-party-saml.xsd
urn:mace:shibboleth:2.0:metadata classpath:/schema/shibboleth-2.0-metadata.xsd
urn:mace:shibboleth:2.0:resource classpath:/schema/shibboleth-2.0-resource.xsd
urn:mace:shibboleth:2.0:security classpath:/schema/shibboleth-2.0-security.xsd
urn:mace:shibboleth:2.0:security:saml classpath:/schema/shibboleth-2.0-security-policy-saml.xsd
urn:oasis:names:tc:SAML:2.0:metadata classpath:/schema/saml-schema-metadata-2.0.xsd">
<rp:AnonymousRelyingParty provider=https://shibboleth.xyz.edu/shibboleth-idp defaultSigningCredentialRef="xyz_creds" />
<rp:DefaultRelyingParty provider="https://shibboleth.xyz.edu/shibboleth-idp" defaultSigningCredentialRef="xyz_creds">
<rp:ProfileConfiguration xsi:type="saml:ShibbolethSSOProfile" includeAttributeStatement="false" assertionLifetime="PT5M" signResponses="conditional" signAssertions="never" />
...<rp:ProfileConfiguration xsi:type="saml:SAML2SSOProfile" includeAttributeStatement="true" assertionLifetime="PT5M" assertionProxyCount="0" signResponses="never" signAssertions="always" encryptAssertions="conditional" encryptNameIds="never" />
</rp:DefaultRelyingParty>
<rp:RelyingParty id=https://xyz.abc.com" provider="https://shibboleth.xyz.edu/shibboleth-idp" defaultSigningCredentialRef="xyz_creds">
<rp:ProfileConfiguration xsi:type="saml:SAML2SSOProfile" signResponses="never" signAssertions="always" encryptNameIds="never" encryptAssertions="never" />
<rp:ProfileConfiguration xsi:type=" saml:SAML2AttributeQueryProfile" signResponses="never" signAssertions="always" encryptNameIds="never" encryptAssertions="never" />
<rp:ProfileConfiguration xsi:type=" saml:SAML2ArtifactResolutionProfile" signResponses="never" signAssertions="always" encryptNameIds="never" encryptAssertions="never" />
</rp:RelyingParty>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170320/6a614710/attachment.html>
More information about the users
mailing list