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.

首先追踪设置 are_multiple_claim_values_allowed 如何应用于 scope 内的 claims，重点关注 eduperson_affiliation 和 eduperson_principal_name。将当前行为与建议的 claim 级别和 scope 级别替代方案进行比较。当项目针对单值 claims 和多值 claims 形成一条经过同意且可预测的规则，并由相关测试覆盖时，即视为完成。