Difference in Release Consent and aacli.sh names from attribute registry

[Cantor, Scott]

On 5/24/22, 10:38 PM, "users on behalf of Lipscomb, Gary via users" <users-bounces at shibboleth.net on behalf of users at shibboleth.net> wrote:

> I'm find an issue with the attribute-registry configuration that if I don't specify a language [1] the consent
> release view  displays the saml2.name but aacli.sh displays the Friendly Name

AACLI just displays either the attribute ID (in the JSON output) or will encode the Attribute into SAML if there's a rule for that. FriendlyName is always included in the XML and falls back to the attribute ID if there's no friendlyName property.

You cannot make friendlyName language specific, all you're doing there is just hiding the setting. The documentation should not be suggesting that you can do that. FriendlyName is not for user consumption so it has no need to be language aware.

I don't know what consent does in various cases, but it can't be relying on the SAML name (it's not known at that point), so that's not possible. It's probably falling back to Attribute ID if the lang matching fails or there's no displayName property.

-- Scott