Expected behavior of Template AttributeDefinition with inconsistent sources
cantor.2 at osu.edu
Mon Sep 16 08:45:43 EDT 2019
On 9/14/19, 12:07 PM, "users on behalf of Takeshi NISHIMURA" <users-bounces at shibboleth.net on behalf of takeshi at nii.ac.jp> wrote:
> You explained in:
> that non-paired values produces values with another attribute as empty in the latest version.
I don't know what you mean by non-paired values but the only change we made is to carve out an exception for attributes that don't exist (have no values), to allow those to be ignored instead of causing failures.
I don't believe there are any changes warranted or what safety issue you think exists.
More information about the users