You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7890452
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: mcp_server/README.md
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,7 @@ instances:
44
44
token_file: "/run/secrets/production-a.token"
45
45
timeout: 30
46
46
debug: false
47
+
ca_file: ""
47
48
insecure_skip_verify: false
48
49
49
50
- id: "production-b"
@@ -52,15 +53,23 @@ instances:
52
53
token_file: "/run/secrets/production-b.token"
53
54
timeout: 30
54
55
debug: false
56
+
ca_file: ""
55
57
insecure_skip_verify: false
56
58
```
57
59
58
60
`LISTEN_ADDRESS` and `LISTEN_PORT` override listener settings. There is deliberately no global `SAFELINE_API_TOKEN`: every instance uses a separate token file.
59
61
62
+
`ca_file`is the certificate authority that signed the certificate of the
63
+
instance. A SafeLine console serves the certificate it generated for itself,
64
+
which no public authority signed: point `ca_file` at that certificate (or at the
65
+
authority that issued it) and the connection stays verified. Relative paths are
66
+
resolved from the directory of the configuration file.
67
+
60
68
`insecure_skip_verify`disables TLS verification for the SafeLine API. The API
61
69
Token is an administrator credential that is sent on every request, so leave the
62
-
setting at `false` and give the instance a certificate the server trusts. Enable
63
-
it only for a lab instance whose certificate cannot be replaced.
70
+
setting at `false` and use `ca_file` for an instance with a self-signed
71
+
certificate. Setting it to `true` logs a warning at startup, and it cannot be
72
+
combined with `ca_file`.
64
73
65
74
Each `display_name` must be unique, ignoring letter case, and must not match another instance's `id`. During server discovery (or legacy initialization), the server publishes only the `display_name` to `instance_id` mappings as Server Instructions. This lets a user refer to a friendly name while the AI still calls `get_attack_events` with the stable, explicit `instance_id`. Instance addresses and credentials are never included in those instructions.
0 commit comments