feat(KLEF): Wire up JWTValidator from the SDK in client.go/jwks.go - #12
Merged
Conversation
isaacwallace123
approved these changes
Apr 13, 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
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.
Pull Request
Summary
Integrates the new
JWTValidatorfrom the Go Plugin SDK, deprecating the custom JWKS verification logic. Also implements the newly required identity management and session methods for Keycloak.Related Issues
Closes #
Changes
What's Included
jwks.goutilities with the SDK's centralJWTValidator.ChangePassword,ListSessions, andRevokeSessionvia Keycloak's client and gRPC server adapters.Dockerfile.localto support isolated local dev setups.What's Not Included
Testing
How Was This Tested?
plugin-sdk-gomodule.Test Coverage
Breaking Changes
Does this PR introduce breaking changes?
If yes, describe the impact and any required migration steps:
Security Considerations
If any box is checked, describe the security impact and any mitigations applied:
Adopting the SDK validation standardizes the security baseline. Keycloak credentials and session endpoints are now securely delegated back to the platform.
Documentation
Does this PR require documentation updates?
If yes, check all that apply:
README.mdARCHITECTURE.md/docsUI/UX (If Applicable)
Screenshots or recordings:
Pre-Merge Checklist
feat:,fix:,chore:,docs:,refactor:,test:)Reviewer Notes