Add configuration that allows filtering based on known client_id
#100
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
java
question
wontfix
renovate
renovate/manager
cargo
renovate/manager
dockerfile
renovate/manager
git-submodules
renovate/manager
gomod
renovate/manager
kustomize
renovate/manager
kustomize
renovate/manager
maven
renovate/manager
maven
renovate/manager
npm
renovate/manager
pip_requirements
renovate/manager
regex
renovate/manager
renovate-config-presets
renovate/manager
woodpecker
renovate/type
bump
renovate/type
digest
renovate/type
lockFileMaintenance
renovate/type
major
renovate/type
minor
renovate/type
patch
renovate/type
pin
renovate/type
pinDigest
renovate/type
replacement
renovate/type
rollback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference: kokuwaio/keycloak-event-metrics#100
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://github.com/kokuwaio/keycloak-event-metrics/blob/main/src/main/java/io/kokuwa/keycloak/metrics/event/MetricsEventListener.java#L36
If a Keycloak system is under attack by an adversary that is attempting to find vulnerabilities or execute script injection attacks, they may set the
client_id
value to arbitrary values. This can pollute the metrics, and cause an explosion of the counters. In order to mitigate this, I suggest adding a configuration that allows unknown clients to either be ignored, or grouped into anUNKNOWN
client_id
.Let me know what you think, and I'll PR.
Ignoring them may hide the fact that the system is under attack. I would collect the unknown
client_id
inUNKNOWN
as you proposed! Thank you!Released with 1.1.0