Remove JWT key filter from docs #6864
Merged
+3
−50
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
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.
Purge remaining references to (deprecated, long-unused) JWT key filter. This includes removing the vestigial field from some structs and related serialisers, which technically means that if nodes after this change try to interop with very old nodes, they might cause KV serialisation errors. That's unsupported, the
lts_compatibilitytest covers exactly which versions are interoperable, and the only thing we need to maintain for that is the field inset_jwt_issuer(for when this Python infra is speaking to a constitution which still requires the field).Resolves #6589.