NameID Encoders doubts from V2 to V3

[Lalith Jayaweera]

Hi,

It is clear from the below link that some of the encoders(
SAML1StringNameIdentifier and SAML2StringNameID) are deprecated and nameID
encoding not handled in the resolver,


However it is not clear to be what is the new way and how to encode it in
V3, does this mean, if the previous V2 encoding is SAML2StringNameID (as
an e.g.) and we can ignore this in V3 and don't need to do anything with
respect to NameID encoding?

https://wiki.shibboleth.net/confluence/display/IDP30/AttributeResolverConfiguration#AttributeResolverConfiguration-NameIDEncoders


Also if I am not mistaken with the new approach from below V2 resolver
definition as an example, and in new V3, below will split into two, that is
resolver will still continue to have this attribute with
encoding enc:SAML2String but only higligthted *SAML2StringNameID *will be
moved to saml-nameid.xml obviously without *SAML2StringNameID*

Please confirm is that the correct understanding, if so, kind of double
work in two files obviously with clarity

<resolver:AttributeDefinition id="myAttributeID" xsi:type="ad:Simple"
sourceAttributeID="uid">
          <resolver:Dependency ref="myLDAP" />
        <resolver:AttributeEncoder xsi:type="enc:SAML2String" name="UserID"
/>

*<resolver:AttributeEncoder xsi:type="SAML2StringNameID"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
nameFormat="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified" />*

 </resolver:AttributeDefinition>


Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170420/9eb5d483/attachment.html>