Replies: 1 comment
-
There's a reason for that. Neither one of the existing Asymmetric JOSE Key Management Algorithms is fit for a use case like you describe because neither one authenticates the sender. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
One of the requirements for encrypting requests is the ability to use the symmetric encryption key after it has been unwrapped, so that the server can encrypt the response. In most JOSE libraries, there is no access to the unwrapped key, and to work around this, you have to do things like putting an AES key in the payload for the server to use to encrypt the response. Alternatively, you could manually extract and unwrap the second part of the JWE token, but this doesn't seem optimal, as it adds an extra decryption step on top of what the library already does.
I wanted to know if there's a way to make the secret key public or at least retrieve its value? Forcing a fork of the library doesn't seem like an ideal solution either.
jose/src/jwe/flattened/decrypt.ts
Line 245 in affe3f2
to
jose/src/jwe/compact/decrypt.ts
Line 97 in affe3f2
to
Beta Was this translation helpful? Give feedback.
All reactions