Open
Conversation
Implements the client_credentials grant (RFC 6749 §4.4) following the same two-step sealed pattern as JWTProcessorConfig - the caller never sees the plaintext secret or access token. Also extracts a shared sealTokenResponse helper from JWTProcessorConfig so both processors share the response-sealing logic without duplication.
timflyio
approved these changes
Apr 2, 2026
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
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.
HelpScout (and other API platforms) use the OAuth2 client_credentials grant for M2M auth, which tokenizer had no native support for. Without it, the client secret had to be stored and managed outside tokenizer, defeating the point, or the token had to be continually refreshed.
Implements RFC 6749 §4.4 following the same two-step sealed pattern as jwt_processor - the caller never sees the plaintext secret or access token.
Also extracts a shared sealTokenResponse helper so JWT and client_credentials don't duplicate the response-sealing logic.