IDP - AtrtibuteResolver - how to map a customAtrribute to Standard SAML attribute
David Bantz
dabantz at alaska.edu
Mon Aug 5 19:10:15 EDT 2013
&$%^ spell check - that's pvid not paid
On Mon, 5 Aug 2013, at 15:08 , David Bantz <dabantz at alaska.edu> wrote:
> Remove the extra spaces in the sourceAttributeID in the employeeNumber attribute that are not present in the paid definition.
>
> David Bantz
>
>
> On Mon, 5 Aug 2013, at 14:13 , "Vignesh, Vanna G." <vignesh at musc.edu> wrote:
>
>> Scott,
>>
>> Is there any difference between passing an attribute to a standard SAML2 attribute or to a custom attribute. In my case, passing value to the custom attribute works. In the logs, I could see onlt the custom attribute passed but not employeeNumber.
>>
>> <resolver:AttributeDefinition id="pvid" xsi:type="ad:Simple" sourceAttributeID="empID">
>> <resolver:Dependency ref="AuthLDAP" />
>> <resolver:AttributeEncoder xsi:type="enc:SAML1String" name="urn:oid:1.3.6.1.4.1.17033.1.1.1.2" />
>> <resolver:AttributeEncoder xsi:type="enc:SAML2String" name="urn:oid:1.3.6.1.4.1.17033.1.1.1.2" friendlyName="pvid" />
>> </resolver:AttributeDefinition>
>>
>> <resolver:AttributeDefinition id="employeeNumber" xsi:type="ad:Simple" sourceAttributeID=" empID ">
>> <resolver:Dependency ref="AuthLDAP" />
>> <resolver:AttributeEncoder xsi:type="enc:SAML1String" name="urn:mace:dir:attribute-def:employeeNumber" />
>> <resolver:AttributeEncoder xsi:type="enc:SAML2String" name="urn:oid:2.16.840.1.113730.3.1.3" friendlyName="employeeNumber" />
>> </resolver:AttributeDefinition>
>>
>> --
>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130805/3df64062/attachment.html
More information about the users
mailing list