-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IdentityProviderBranding
field name
should provide lang and direction
#679
Comments
+1 to Christian's comment in the other issue that generally names are not localizable. Although it can be argued that company names are, they are not directly translateable so the IDP would have to provide a dictionary of languages to names in that language. Is that what you are suggesting? |
Please note that we are not requesting localizability here, merely that there be a means of associating language and direction metadata with the |
That might more or less work for this issue, but for #680 how do you expect the IDP to provide a language/direction? Not a single website has ever asked me what language or direction my name is in, and I don't even think that question makes sense for names. |
Usually it is computed from the user's locale or locale preference. I agree it would be an unusual interface to specifically ask you for the language of your name. The base direction is known (or can be known) from the |
In SAML Metadata, there is a specification that describes how entities (IdP in the case here) can 'provide information necessary for user agents to present effective user interfaces'. This might be useful here. Essentially, an IdP can do exactly what @npm1 suggests, have more than one displayName, privacy statement etc. in different languages. For example (in XML):
The Identity Provider discovery service can then use the locale of the browser to determine which to show (with a default). |
If the SAML case is of interest, here are the top 6 IdP languages used in the R&E eduGAIN federation of federations:
|
Adding language makes sense; adding direction is not harmful but is questionably useful. (Discussed 11 February 2025 call). @cbiesinger to make a spec PR |
IdentityProviderBranding
https://w3c-fedid.github.io/FedCM/#dictdef-identityproviderbranding
https://w3c-fedid.github.io/FedCM/#dom-identityproviderbranding-name
There is no language or direction metadata associated with these natural language string values (see String-Meta and our Best Practices for more info).
The text was updated successfully, but these errors were encountered: