resolves #321, Added support for passing additional headers in JWE encryption. #323
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… JWE encryption.
|
I'll request maintainers of the repo to approve the waiting workflow (for linting) and also to review the PR. |
|
Friendly nudge to look into this PR. |
|
Any update on this? cc: @mpdavis |
|
Any update on this? |
|
@mpdavis / other-maintainers, Any update on this? The PR is now open for more than 6 months. |
|
Looks like the project is not maintained anymore? I hope someone forks the project for further maintainance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JWS and JWE, both spec have the provision of custom (i.e. user-defined) headers. python-jose supports passing custom headers in the
headersparameter injose.jws.sign()method. But the same is not supported injose.jwe.encrypt()method. This pull-request adds this support.