Skip to content

Security/Crowdsec: UI support for remote LAPI in the remediation component - #5754

Open
MichaelPihlblad wants to merge 1 commit into
opnsense:masterfrom
MichaelPihlblad:crowdsec-remote-lapi
Open

MichaelPihlblad wants to merge 1 commit into
opnsense:masterfrom
MichaelPihlblad:crowdsec-remote-lapi

Conversation

@MichaelPihlblad

Copy link
Copy Markdown
  • add "Remote LAPI" option (URL, write-only API key) for the bouncer
  • check status only for enabled services, one service entry each
  • add overview page with bouncer status and connection test
  • add "Blocked by this firewall" tab to decisions

Solves: #5753

Important notices

Before you submit a pull request, we ask you kindly to acknowledge the following:

If AI was used, please disclose:

  • Model used: Opus 5.5
  • Extent of AI involvement: High

Describe the problem
Using the firewall bouncer with a LAPI on another host currently needs manual YAML edits, and the
plugin shows an error because it always checks the disabled crowdsec service.


Describe the proposed solution

  • Implement UI support for remote LAPI in the remediation component.
  • Check plugin status only for enabled services

Related issue
#5753

…onent

- add "Remote LAPI" option (URL, write-only API key) for the bouncer
- check status only for enabled services, one service entry each
- add overview page with bouncer status and connection test
- add "Blocked by this firewall" tab to decisions

Solves: opnsense#5753
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant