feat(lib): Add option for adding difficulty field to JWT claims #1063
Conversation
This file contains hidden or 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
Earl0fPudding
changed the title
Contributor
Author
|
Spelling and translation were needed for the checks to pass. It has nothing to do with my changes per se. |
Xe
approved these changes
Sep 11, 2025
Xe
force-pushed
the
difficulty-jtw-field
branch
from
8018e95 to
54c6cd5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi Xe,
It's me again.
This change adds the
DIFFICULTY_IN_JWToption, which allows one to add thedifficultyfield in the JWT claims which indicates with which difficulty the token has been generated.In my case, I need it for routing my requests to Anubis in HAProxy based on this field. It can also be used for debugging purposes and so on.
Please let me know if this is OK or a separate test case is needed.
This is not a breaking change as this new option is false by default. I also simplified the MapClaims logic a bit.
Many thanks,
Martin
Checklist:
[Unreleased]section of docs/docs/CHANGELOG.mdnpm run test:integration(unsupported on Windows, please use WSL)