Add generating signed JWT tokens #119
Draft
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
fix: create var for repeated usage error
|
If this project is no longer actively maintained, or this feature is definitely not something desired, please let me know. If I need to implement this elsewhere, that's fine with me. |
fix: use jwt time fields correctly
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.
This is still a WIP, but feel free to comment.
The ultimate goal of this feature is to enable
smimesignto be used as an authentication method for Hashicorp Vault. Once the JWT is generated and signed, it can be passed to Vault's JWT Authentication method.More details will be added here when/if I figure out if they actually work.