Current document root:
IETF RFC 9396
Click a document below to open its own reference tree.
Level 1 — direct dependents (docs that cite this doc)
- IETF RFC 9700[Active*]
Level 1 — direct references (docs this doc cites)
- ETSI.TS-119-432.2019ETSIEXTERNAL
- IETF RFC 20[Active*]
- IETF RFC 2119[Active*]
- IETF RFC 6749[Active*]
- IETF RFC 7519[Active*]
- IETF RFC 7591[Active*]
- IETF RFC 7662[Active*]
- IETF RFC 8174[Active*]
- IETF RFC 8259[Active*]
- IETF RFC 8414[Active*]
- RFC8628RFC8628EXTERNAL
- IETF RFC 8707[Active*]
- IETF RFC 9101[Active*]
- IETF RFC 9126[Active*]
- Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., and C. Mortimore, "OpenID Connect Core 1.0 incorporating errata set 1", 8 November 2014, <https://openid.net/specs/openid-connect-core-1_0.html>.EXTERNAL
- IANA, "OAuth Parameters", <https://www.iana.org/assignments/oauth-parameters>.EXTERNAL
- Fernandez, G., Walter, F., Nennker, A., Tonge, D., and B. Campbell, "OpenID Connect Client-Initiated Backchannel Authentication Flow - Core 1.0", 1 September 2021, <https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html>.EXTERNAL
- OpenJS Foundation, "JSON Schema", <https://json-schema.org/>.EXTERNAL
- Lodderstedt, T., "Transaction Authorization or why we need to re-think OAuth scopes", 20 April 2019, <https://medium.com/oauth-2/transaction-authorization-or-why-we-need-to-re-think-oauth-scopes-2326e2038948>.EXTERNAL
- Cloud Signature Consortium, "Architectures and protocols for remote signature applications", Version 1.0.4.0, June 2019, <https://cloudsignatureconsortium.org/wp-content/uploads/2020/01/CSC_API_V1_1.0.4.0.pdf>.EXTERNAL