decoding: add decode_header_as function
#445
Open
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
Headers may contain custom fields. As an example, these fields may be used by implementations to choose the decoding key rather than disabling signature validation, parsing the payload, determining the key and *then* decoding securely. RFC 7519 § 5.3 explicitly calls out the ability to store `iss`, `sub`, and `aud` in the header. Using custom structures also allows users to avoid storing any unnecessary data when doing such pre-processing. See: https://datatracker.ietf.org/doc/html/rfc7519#section-5.3 Fixes: Keats#435
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Headers may contain custom fields. As an example, these fields may be used by implementations to choose the decoding key rather than disabling signature validation, parsing the payload, determining the key and then decoding securely.
RFC 7519 § 5.3 explicitly calls out the ability to store
iss,sub, andaudin the header.Using custom structures also allows users to avoid storing any unnecessary data when doing such pre-processing.
See: https://datatracker.ietf.org/doc/html/rfc7519#section-5.3
Fixes: #435