9.4.1. Registry Contents
9.4.1. Registry Contents
This section registers the application/oauth-authz-req+jwt media type [RFC2046] in the "Media Types" registry [IANA.MediaTypes] in the manner described in [RFC6838]. It can be used to indicate that the content is a JWT containing Request Object claims.
| Field | Value |
|---|---|
| Type name | application |
| Subtype name | oauth-authz-req+jwt |
| Required parameters | N/A |
| Optional parameters | N/A |
| Encoding considerations | binary; a Request Object is a JWT; JWT values are encoded as a series of base64url-encoded values (some of which may be the empty string) separated by period (.) characters. |
| Security considerations | See Section 10 of RFC 9101 |
| Interoperability considerations | N/A |
| Published specification | Section 4 of RFC 9101 |
| Applications that use this media type | Applications that use Request Objects to make an OAuth 2.0 authorization request |
| Fragment identifier considerations | N/A |
| Deprecated alias names for this type | N/A |
| Magic number(s) | N/A |
| File extension(s) | N/A |
| Macintosh file type code(s) | N/A |
| Person & email address to contact for further information | Nat Sakimura [email protected] |
| Intended usage | COMMON |
| Restrictions on usage | none |
| Author | Nat Sakimura [email protected] |
| Change controller | IETF |
| Provisional registration? | No |