Increase Canton JWT expiry #2349
Merged
+2
−1
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
skudasov
approved these changes
Jan 19, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR extends the JWT token expiry duration for Canton authentication from 24 hours to 10 years, significantly reducing the frequency of required re-authentication. The change is documented in the changelog.
Changes:
- JWT token expiry increased from 1 day to 10 years in Canton configuration
- Changelog updated to reflect the JWT expiry change
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| framework/components/blockchain/canton.go | Modified TokenExpiry constant to extend token validity to 10 years |
| framework/.changeset/v0.13.3.md | Added changelog entry documenting the JWT token expiry increase |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes were made to improve the authentication mechanism in a blockchain framework by extending the JWT token expiry, enhancing security, and user experience by reducing the frequency of re-authentication.
What
TokenExpiryconstant fromtime.Hour * 24to a more extended period represented by a cryptic string suggesting a significant increase, possibly aiming for a 10-year token validity period. This change in token expiry duration directly impacts the authentication token's longevity, presumably to decrease the need for frequent renewals in long-term operations.