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.

Sign up for GitHub

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

Jump to bottom

parsePlaintext* methods should declare byte array types, not strings #274

Closed
lhazlewood opened this issue Nov 1, 2017 · 1 comment
Closed

parsePlaintext* methods should declare byte array types, not strings #274

lhazlewood opened this issue Nov 1, 2017 · 1 comment
Milestone
0.12.0

Comments

@lhazlewood
Copy link
Contributor

lhazlewood commented Nov 1, 2017 •
edited
Loading

RFC 7515, Section 2 states:

JWS Payload
The sequence of octets to be secured -- a.k.a. the message. The
payload can contain an arbitrary sequence of octets.

This is reinforced by the example shown in Appendix A4 using a payload of the string literal Payload.

As such, the JJWT API needs to be changed to reflect byte[] types and not String. This change would be backwards incompatible so it is slated for 1.0.
@lhazlewood lhazlewood added this to the 1.0 milestone Nov 1, 2017
@lhazlewood lhazlewood changed the title Remove parsePlaintext* method variants parsePlaintext* methods should declare byte array types, not strings Aug 20, 2018
@lhazlewood lhazlewood modified the milestones: 1.0, 0.12.0 Aug 11, 2023
@lhazlewood
Copy link
Contributor Author

lhazlewood commented Aug 11, 2023 •
edited
Loading

Merged with #279 , will be released in 0.12.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.12.0
Development

No branches or pull requests
1 participant
@lhazlewood