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.

Empieza trazando cómo se aplica la configuración are_multiple_claim_values_allowed a los claims dentro de un scope, centrándote en eduperson_affiliation y eduperson_principal_name. Compara el comportamiento actual con las alternativas propuestas a nivel de claim y a nivel de scope. Se considera terminado cuando el proyecto tenga una regla acordada y predecible para claims de un solo valor y de múltiples valores, cubierta por las pruebas relevantes.