A CrowdSec Bouncer that syncs the decisions made by CrowdSec with CloudFlare's firewall. Manages multi user, multi account, multi zone setup. Supports IP, Country and AS scoped decisions.
MIT License
50
stars
7
forks
source link
bouncer -g command line merges API's from multiple accounts into the first acccount ID. #119
When for example when you are running the command line crowdsec-cloudflare-bouncer -g API1, API2, it merges the zones from all other API's into the first api with as example:
accounts:
- id: xxx EMAIL's Account
zones:
- zone_id: ID1 #website1 <- this is correct
actions:
- managed_challenge
- zone_id: ID2 #website2 <- Incorrect, belongs to the second API
actions:
- managed_challenge
- zone_id: ID3 #website3 <- Incorrect, belongs to the second API
actions:
- managed_challenge
token: token
ip_list_prefix: crowdsec
default_action: managed_challenge
total_ip_list_capacity: 10000 # only this many latest IP decisions would be kept
- id: xxx #second token email
zones: []
token: token
ip_list_prefix: crowdsec
default_action: managed_challenge
total_ip_list_capacity: 10000 # only this many latest IP decisions would be kept
update_frequency: 10s
It does properly add the ID/Email and token of the second API into the config file, just not the zones.
When for example when you are running the command line crowdsec-cloudflare-bouncer -g API1, API2, it merges the zones from all other API's into the first api with as example:
It does properly add the ID/Email and token of the second API into the config file, just not the zones.