- changed milestone to Implementer's Draft
Support for different languages for the client_name
Issue #64
new
In the OpenID Connect Dynamic Client Registration specification, client_name is defined (Name of the Client to be presented to the End-User) with option ("if desired") of defining this Claim in different languages.
For example, values such as client_name, tos_uri, policy_uri, logo_uri, and client_uri might have multiple locale-specific values in some Client registrations. Language tags (per RFC5646) can be added to the Client Metadata member names.
For MODRNA, SHOULD client_name support different languages?
Comments (1)
-
reporter
- Log in to comment
- Assignee
- Type
- Priority
- Status
- new
- Component
- Registration
- Milestone
- Implementer's Draft
- Votes
- 0
- Watchers
- 0
In the OpenID Connect Dynamic Client Registration specification, client_name is defined (Name of the Client to be presented to the End-User) with option ("if desired") of defining this Claim in different languages.
For example, values such as client_name, tos_uri, policy_uri, logo_uri, and client_uri might have multiple locale-specific values in some Client registrations. Language tags (per RFC5646) can be added to the Client Metadata member names.
For MODRNA, SHOULD client_name support different languages?