Implement RFC-7797 / JWS (Detached Payload)

[loganvolkers]

JSON Web Signature (JWS) represents the payload of a JWS as base64url-encoded value and uses this value in the JWS Signature computation.

While this enables arbitrary payloads to be integrity protected, some have described use cases in which the base64url encoding is unnecessary and/or an impediment to adoption, especially when the payload is large and/or detached. This specification defines a means of accommodating these use cases by defining an option to change the JWS Signing Input computation to not base64url-encode the payload. This option is intended to broaden the set of use cases for which the use of JWS is a good fit.

Please consider implementing Detached Payload support.

[blag]

I would happily review and merge a pull request implementing this.

[AFlowOfCode]

For reference: https://datatracker.ietf.org/doc/html/rfc7797

@blag if you would still happily review and merge a pull request, it looks like @finvu has one linked to this issue, which @chayan-datta approved in March.

In any case support for this enhancement plus the elimination of the incorrectly hardcoded {"typ": "JWT"} header for JWSs (#204) would be excellent to see in this library. The proposed merge requests for this & #204 hardly seem complicated so why they are not being merged as the years go by is a bit baffling.

[PSoltes]

any updates to this? it seems PRs are created and ready just not merged and released

[AFlowOfCode]

@PSoltes At this point I think it's safe to say this project is essentially abandoned. The contributors are not around anymore or not interested in PRs or improvements in general. If you look at the commits, there's hardly been any real work done since early 2021.