Security · umbrella · IETF — JOSE working group (active; rechartered for JSON Web Proofs and new algorithms)

JOSE (JSON Object Signing and Encryption)

JOSE is the IETF family of specifications for signing, encrypting and carrying claims as JSON — the framework JSON Web Tokens come from. It defines JSON Web Signature (JWS, RFC 7515) for integrity-protected objects, JSON Web Encryption (JWE, RFC 7516) for encrypted objects, JSON Web Key (JWK, RFC 7517) for representing keys, JSON Web Algorithms (JWA, RFC 7518) for the algorithms all of them use, and JSON Web Token (JWT, RFC 7519) for compact claims. A JOSE object carries its own processing instructions in a protected header alongside its payload, which is what makes it powerful and hard to describe from a schema alone. The IETF JOSE working group is active again, working on JSON Web Proofs, post-quantum algorithms and deprecating unsafe options.

datatracker.ietf.org/wg/jose/ab...The standard
IETF — JOSE working group (active; rechartered for JSON Web Proofs and new algorithms)Governing body
2015First published
RFC 7515–7520 (2015); active drafts i...Current version
0providers in the catalog

Also known as JSON Object Signing and Encryption, Javascript Object Signing and Encryption, application/jose.

Providers that carry JOSE 0

No provider in the catalog carries this standard as a tag yet. That is a statement about the catalog's tagging, not about adoption: a provider that implements JOSE and says so in its APIs.json profile appears here on the next build. Add or correct a listing.

Reading

Read from the API Evangelist standards directory, facts verified 2026-10-08. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.