b_c / jose4j / issues / #99 - allow JWS payload to be an arbitrary sequence of bytes — Bitbucket

Issue #99 closed

Brian Campbell repo owner created an issue 2017-07-08

Currently the JsonWebSignature payload is assumed/required to be a String. And while it usually will be a string in typical usage, per RFC 7515 the "payload can contain an arbitrary sequence of octets" and the jose4j API should allow for that.

Comments (3)

Brian Campbell reporter
- changed title to allow JWS payload to be an arbitrary sequence of bytes
- 2017-07-09T20:25:31+00:00
Brian Campbell reporter
- changed status to resolved
done with https://bitbucket.org/b_c/jose4j/commits/02caefb97c2440c7f84f4857ada3cee4fcce393d and JsonWebSingature now has getPayloadBytes(), getUnverifiedPayloadBytes() and setPayloadBytes(byte[] payloadBytes) in addition to the String based payload methods
- 2017-07-09T20:29:51+00:00
Brian Campbell reporter
- changed status to closed
released in v0.6.0
- 2017-07-24T19:58:01+00:00
Log in to comment

Assignee: Brian Campbell

Type: bug

Priority: minor

Status: closed

Votes: 0

Watchers: 1

Jira: the preferred issue tracker for Bitbucket. Join the team!