Attributes being removed from SAML1 Service Provider because they cannot be encoded.

[Cantor, Scott E.]

On 8/2/11 1:28 PM, "Cantor, Scott E." <cantor.2 at osu.edu> wrote:
>
>>I'm kinda lost here. Do I define a new parameter as a SAML1String using
>>the OID and how do I push those attributes via SAML1?
>
>You may be able to add a a second SAML 1 encoder to the existing EPPN
>definition with the OID specified and it will generate both.

This works, my way was just extra work.

e.g.

<resolver:AttributeDefinition xsi:type="ad:Scoped"
id="eduPersonPrincipalName"
	scope="osu.edu" sourceAttributeID="name">
	<resolver:Dependency ref="account" />

	<resolver:AttributeEncoder xsi:type="enc:SAML1ScopedString"
	name="urn:mace:dir:attribute-def:eduPersonPrincipalName" />
	<resolver:AttributeEncoder xsi:type="enc:SAML1ScopedString"
  	name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6" scopeType="inline" />
	<resolver:AttributeEncoder xsi:type="enc:SAML2ScopedString"
	name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6"
	friendlyName="eduPersonPrincipalName" />
    </resolver:AttributeDefinition>


-- Scott