Expected behavior of Template AttributeDefinition with inconsistent sources
Takeshi NISHIMURA
takeshi at nii.ac.jp
Thu Jul 18 11:58:39 EDT 2019
Hi all,
What is the expected behavior of Template AttributeDefinition with inconsistent sources?
Undefined?
It seems that the behavior changed between 3.3.1 and 3.4.3.
When uid has one value and mail has no values, 3.3.1 seems to throw an exception and 3.4.3 seems to produce "$mail" literally.
<AttributeDefinition xsi:type="Template" id="testMail1">
<InputDataConnector ref="myLDAP" attributeNames="uid mail" />
<AttributeEncoder xsi:type="SAML1String" name="urn:mace:dir:attribute-def:mail" encodeType="false" />
<AttributeEncoder xsi:type="SAML2String" name="urn:oid:0.9.2342.19200300.100.1.3" friendlyName="mail" encodeType="false" />
<Template>
<![CDATA[
#if($uid=="student1")student1+ext1 at example.ac.jp#elseif($uid=="student2")student2+ext2 at example.ac.jp#else$mail#end
]]>
</Template>
</AttributeDefinition>
Best regards,
Takeshi
More information about the users
mailing list