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 for Non-JSON Formatted Payload #40

Open
justkash opened this issue Oct 8, 2024 · 1 comment
Open

Support for Non-JSON Formatted Payload #40

justkash opened this issue Oct 8, 2024 · 1 comment

Comments

@justkash
Copy link

justkash commented Oct 8, 2024

Should PASETO be agnostic to the formatting of the payload? Is there a strong reason why JSON payloads are preferred?

@justkash justkash changed the title Support for Non-JSON formatted Payload Support for Non-JSON Formatted Payload Oct 8, 2024
@paragonie-security
Copy link
Contributor

We went with JSON because it was convenient, especially for developers that would otherwise reach for JWTs.

Other encodings are tentatively permitted by the spec, should anyone care to specify them. We even called out v3c / v4c as a potential header for "CBOR".

But we don't use anything other than JSON in our own projects, so we haven't felt a need to specify it.

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

2 participants