v0.36.1

integrations/opnsense-acme/README.md

@@ -5,7 +5,7 @@ A simple mechanism for automatically sending a certificate generated by `os-acme
 ## Files
 
 - `opnsense-rustproxy-cert-deploy.sh` - sends the certificate and private key to RustProxy.
-- `rustproxy-acme.conf` - connection settings, API token, and certificate file paths.
+- `rustproxy-acme.conf.example` - example connection settings, API token, and certificate file paths.
 - `actions_rustproxy_cert.conf` - optional `configd` action that allows the script to be executed from Cron in OPNsense.
 
 ## 1. Installation
@@ -50,13 +50,15 @@ KEY_FILE='/path/to/private.key'
 
 ## 3. RustProxy API
 
-Create a certificate API key in RustProxy and enter its values in the configuration:
+Create a certificate API key in **Settings -> Certificate API** and enter its values in the configuration:
 
 ```text
 RUSTPROXY_KEY_ID
 RUSTPROXY_TOKEN
 ```
 
+The credential must explicitly allow `CERTIFICATE_ID` and **Also allow deploy** (`allow_deploy`) must be enabled. A reload-only credential will be rejected with HTTP 403.
+
 The script sends the certificate to:
 
 ```text
@@ -88,7 +90,7 @@ cp actions_rustproxy_cert.conf /usr/local/opnsense/service/conf/actions.d/
 service configd restart
 ```
 
-Then go to **System -> Settings -> Cron** and add a scheduled execution of the `Deploy ACME certificate to RustProxy` action.
+Verify the action first with `configctl rustproxy_cert deploy`. Then go to **System -> Settings -> Cron** and add a scheduled execution of the `Deploy ACME certificate to RustProxy` action.
 
 The script deliberately reconciles on every run instead of trusting a local cache. The server is the source of truth: an identical RustProxy-owned certificate generation is a no-op, a missing id is created, and changed material is rotated atomically. This also repairs drift when a certificate entry or generation was removed outside OPNsense.