[SYNCOPE-1976] Add configurable REST rate limiting#1420
Merged
Conversation
ilgrosso
requested changes
Jun 10, 2026
ilgrosso
left a comment
Member
There was a problem hiding this comment.
The filter is now defined, tested and added to the Spring context, but not actually configured in CXF.
You will need to add it in IdRepoRESTCXFContext#restContainer to do so.
54c6fd9 to
a6d65fd
Compare
b8a29a5 to
cad8332
Compare
Member
|
@massx1 the PR looks ok now, can you add some notes to the reference guide about this feature? |
ilgrosso
approved these changes
Jun 15, 2026
massx1
added a commit
that referenced
this pull request
Jun 15, 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.
Adds optional REST rate limiting for Syncope Core APIs.
The feature allows administrators to configure request thresholds, time windows, lock periods, trusted proxies, and excluded client addresses (for example Console instances).
When enabled, clients exceeding the configured threshold receive 429 Too Many Requests with a Retry-After header.
The feature is disabled by default.
Notes
This is intended as a lightweight L7 mitigation for excessive request rates against CXF REST endpoints, complementing existing endpoint-specific throttling such as login and password reset protection.