Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support (RFC7797) Unencoded Payload Option #68

Open
kjvalencik opened this issue Jul 17, 2017 · 0 comments
Open

Support (RFC7797) Unencoded Payload Option #68

kjvalencik opened this issue Jul 17, 2017 · 0 comments

Comments

@kjvalencik
Copy link

kjvalencik commented Jul 17, 2017

RFC7797 defines an extension to JSON Web Signatures to allow unencoded payloads.

Additional features

Recommended API Changes

Add opts.detached

Default: false. When opts.detached === false, the payload is omitted from the payload. The separators remain where it would usually be. E.g.,

eyJhbGciOiJIUzI1NiIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..A5dxf2s96_n5FLueVuW1Z_vh161FwXZC4YLPff6

Add opts.header.b64

Default: true. When b64 is false, the payload will not be encoded prior to signing.

Since, unencoded and detached are most useful together for large bodies, we would stream the data to sign. This would require a change to jwa in order to support this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant