are_multiple_claim_values_allowed controls all claims in a scope

If I set are_multiple_claim_values_allowed to true in a custom scope eduperson, which I need for eduperson_affiliation, eduperson_principal_name also becomes a list even if it contains only one value (and is defined as single-valued).
Maybe the are_multiple_claim_values_allowed setting should live at the claim definition level instead of scope?

Or: Always send single valued claims as string and expand to list if are_multiple_claim_values_allowed is set to true at the scope level, this would be the least intrusive refactor. But the downside is that this behaviour would be unpredictable for the RP.

まず、スコープ内の claims に設定 are_multiple_claim_values_allowed がどのように適用されるかを追跡し、eduperson_affiliation と eduperson_principal_name に焦点を当てます。現在の動作を、提案されている claim レベルおよびスコープレベルの代替案と比較します。プロジェクトで単一値 claims と複数値 claims に対する合意済みの予測可能なルールが定められ、関連するテストでカバーされていれば完了です。