tos_
Registry Context
`tos_uri` is the URL of the client’s human-readable terms-of-service document for end-users.
Technical Summary
`tos_uri` is client metadata containing a URL to a human-readable terms-of-service document describing the contractual relationship that the end-user accepts when authorizing the client. It may have locale-specific variants.
When Used
When registering terms-of-service information associated with an OAuth client.
Normative Requirements
Authorization servers
RFC 7591 - Section 2
display the `tos_uri` URL to the end-user.
Condition: if it is provided
The authorization server SHOULD display this URL to the end-user if it is provided.
Implementations
RFC 7591 - Section 2.2
interpret supplied language-tag values case-insensitively.
Condition: when processing internationalized client metadata member names
implementations SHOULD interpret the language tag values supplied in a case insensitive manner
Unspecified actor
RFC 7591 - Section 2
point to a valid web page.
Condition: as the value of `tos_uri`
The value of this field MUST point to a valid web page.
RFC 7591 - Section 2.2
spell language tags using the character case registered in the IANA Language Subtag registry.
Condition: when language tags are used in client metadata member names
It is RECOMMENDED that language tag values used in Claim Names be spelled using the character case with which they are registered
RFC 7591 - Section 2.2
use an untagged value suitable for display on a wide variety of systems.
Condition: when sending `tos_uri` without a language tag
it is RECOMMENDED that any human-readable fields sent without language tags contain values suitable for display on a wide variety of systems
RFC 7591 - Section 2.2
represent `tos_uri` using multiple languages and scripts.
Condition: as internationalized client metadata
Human-readable client metadata values and client metadata values that reference human-readable values MAY be represented in multiple languages and scripts.
RFC 7591 - Section 2
implement and use the `tos_uri` client metadata field.
Condition: unless another applicable specification states otherwise
implementation and use of all client metadata fields is OPTIONAL, unless stated otherwise
clients and servers
RFC 7591 - Section 2.2
use an untagged `tos_uri` field in addition to language-specific variants.
Condition: when language-specific variants are used
It is RECOMMENDED that clients and servers use a human-readable field without any language tags in addition to any language-specific fields
parties using the field
RFC 7591 - Section 2.2
make assumptions about the language, character set, or script of its value.
Condition: if `tos_uri` is sent without a language tag
parties using it MUST NOT make any assumptions about the language, character set, or script of the string value
RFC 7591 - Section 2.2
use the value as-is wherever it is presented in a user interface.
Condition: if `tos_uri` is sent without a language tag
the string value MUST be used as is wherever it is presented in a user interface
Validation Guidance
Report an error if `tos_uri` does not point to a valid web page; RFC 7591 does not itself require rejection as the processing response.
When `tos_uri` is provided, verify that the authorization server normally displays it to the end-user.
Permit locale-specific forms such as `tos_uri#en` and process their BCP 47 language tags case-insensitively.
For an untagged `tos_uri`, do not infer its language or script and preserve its value when presenting it in a user interface.
When localized variants are used, also provide an untagged `tos_uri` suitable for broad display compatibility.
Reference
Details
- Entry Id
tos_uri - Client Metadata Name
tos_uri - Client Metadata Description
URL that points to a human-readable terms of service document for the client- Change Controller
IESG- Reference
RFC7591