Bouncer not reading API_KEY from environment correctly

iiAmLoz · March 4, 2024, 12:18pm

The documentation you link too is the CrowdSec binary and that does support environment variables, however, bouncers do not we use ${API_KEY} as a placeholder within the post installation scripts to replace with the key it generates.

github.com

crowdsecurity/cs-firewall-bouncer/blob/ee9cca46257035e12c2a4b3a24a02e47a9aa8a9b/scripts/_bouncer.sh#L154


      
                      echo "API Key successfully created" >&2
                      echo "$bouncer_id" > "$CONFIG.id"
                  fi
              else
                  echo "cscli/crowdsec is not present, please set the API key manually" >&2
                  api_key="<API_KEY>"
                  ret=1
              fi
          
              if [ "$api_key" != "" ]; then
                  set_config_var_value 'API_KEY' "$api_key"
              fi
          
              return "$ret"
          }
          
          set_local_port() {
              require 'CONFIG'
              local port
              command -v cscli >/dev/null || return 0
              # the following will fail with a non-LAPI local crowdsec, leaving empty port

Topic		Replies	Views
Firewall bouncer problem	1	353	June 11, 2024
Cs-nginx-bouncer not communicating with LAPI crowdsec	3	1046	February 3, 2022
Iptables bouncer error on apt upgrade	6	949	February 6, 2022
CS-Firewall-Bouncer nftables crowdsec	6	998	March 16, 2022
Crowdsec engine and API on windows bouncer on openwrt issues crowdsec	1	404	January 23, 2024

Bouncer not reading API_KEY from environment correctly

Related topics