-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose CryptoService and RateLimiterRegistry to plugins #6638
Expose CryptoService and RateLimiterRegistry to plugins #6638
Conversation
Signed-off-by: JohnNiang <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6638 +/- ##
============================================
- Coverage 58.18% 58.05% -0.13%
- Complexity 3774 3917 +143
============================================
Files 651 670 +19
Lines 22125 22980 +855
Branches 1538 1576 +38
============================================
+ Hits 12873 13341 +468
- Misses 8641 9022 +381
- Partials 611 617 +6 ☔ View full report in Codecov by Sentry. |
/ping @halo-dev/sig-halo |
/sig docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: guqing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
/area core
/area plugin
/milestone 2.20.x
What this PR does / why we need it:
Currently, we are refactoring login and logout pages to make them extensible. If plugins want to realize a new authentication method, the CryptoService and RateLimiterRegistry may be used to authenticate.
So this PR exposes the two beans to plugins. No side effect will be introduced.
Does this PR introduce a user-facing change?