Custom NameID Generation

[Michael Dahlberg]

>
>
> > So you're saying that 'emailAddress' is a type of format and that 'mail'
> should be released?
>
> I think the confusion here stems from all the different points where
> attributes can be assigned names.  It can have one name in the directory,
> another name internally in the IdP, and another name outbound.
>
> The internal to the IdP stuff is, well, internal.  Any name there can be
> anything you want as long as it’s consistent.  The internal name that ships
> with the IdP changed between v2.4 and v3, but the names on the wire didn’t
> change.
>
> 2.4.5:
>     <resolver:AttributeDefinition xsi:type="ad:Simple" id="email"
> sourceAttributeID="mail”>
>         <resolver:AttributeEncoder xsi:type="enc:SAML2String"
> name="urn:oid:0.9.2342.19200300.100.1.3" friendlyName="mail" />
>
> 3.2.1:
>     <resolver:AttributeDefinition xsi:type="ad:Simple" id="mail"
> sourceAttributeID="mail”>
>         <resolver:AttributeEncoder xsi:type="enc:SAML2String"
> name="urn:oid:0.9.2342.19200300.100.1.3" friendlyName="mail"
> encodeType="false" />
>
>
Thanks, Nate.  I did not change my attribute-resolver.xml file in the
upgrade to v3.  I might need to look at that.

I was looking at the metadata file for this SP (google) and the
saml-nameid.xml file to see if there were inconsistencies or typos.  I
couldn't find any.

I did look at the IdP metadata that I generated from a new install and I
noticed that it contained the following two lines which were completely
generated from the install process:

        <NameIDFormat>urn:mace:shibboleth:1.0:nameIdentifier</NameIDFormat>

<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>

I thought that the "2.0" part was indicative of the SAML version
specification and that there was no "2.0" specification; that "1.1" should
be used instead.  Can you tell me what this field in this specifier
signifies?

Thanks,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160304/0b4f7885/attachment.html>