Sign then encrypt data (nested JWE(JWS))

Performs sign-then-encrypt operation: signs data with signKid, then encrypts
the resulting JWS with encryptKid to produce a nested JWE(JWS) structure.

Both keys must be homogeneous (both symmetric or both asymmetric). Both keys
must be different for security.

Supports SIMPLE keys (Compact JWE/JWS) and COMPOSITE keys (General JSON Serialization).
COMPOSITE keys enable hybrid post-quantum cryptography with dual signatures (COMPOSITE_SIGNATURE)
and combined key encapsulation (COMPOSITE_KEM_COMBINE).

Key type combinations:

  • Symmetric + Symmetric (e.g., AES-GCM + HMAC-SHA256)
  • Asymmetric + Asymmetric (e.g., ML-KEM + ML-DSA, RSA + ECDSA)
  • COMPOSITE + COMPOSITE (e.g., COMPOSITE_KEM_COMBINE + COMPOSITE_SIGNATURE)
  • COMPOSITE + SIMPLE (any homogeneous combination)

The JWE outer header includes cty="JWS" to indicate nested content.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Data to sign and encrypt with two different keys

Request for sign-then-encrypt operation producing nested JWE(JWS).

string
required

Base64-encoded data to sign and encrypt

string
required

Key identifier for signing operation

string
required

Key identifier for encryption operation

int64
1 to 3650

Optional validity period in days for the signature (JWS exp claim)

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json