https://github.com/spiffe/spiffe-helper
The SPIFFE Helper is a tool that can be used to retrieve and manage SVIDs on behalf of a workload
https://github.com/spiffe/spiffe-helper
Last synced: about 2 months ago
JSON representation
The SPIFFE Helper is a tool that can be used to retrieve and manage SVIDs on behalf of a workload
- Host: GitHub
- URL: https://github.com/spiffe/spiffe-helper
- Owner: spiffe
- License: apache-2.0
- Created: 2017-10-06T02:43:58.000Z (over 7 years ago)
- Default Branch: main
- Last Pushed: 2024-10-18T05:47:27.000Z (8 months ago)
- Last Synced: 2024-10-18T15:47:09.167Z (8 months ago)
- Language: Go
- Homepage:
- Size: 339 KB
- Stars: 45
- Watchers: 16
- Forks: 40
- Open Issues: 27
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: CODEOWNERS
Awesome Lists containing this project
- awesome-spiffe-spire - SPIFFE Helper
README
> # Help improve SPIFFE Helper
>
> Fill out this [questionnaire](https://docs.google.com/forms/d/1MwHyAiLXnGuUpymwBCfBJei25lur2jaD-056L5Hp1Js) so we can learn more about your use case.
# SPIFFE Helper
The SPIFFE Helper is a simple utility for fetching X.509 SVID certificates from the SPIFFE Workload API, launch a process that makes use of the certificates and continuously get new certificates before they expire. The launched process is signaled to reload the certificates when is needed.
## Usage
`$ spiffe-helper -config `
``: file path to the configuration file.
If `-config` is not specified, the default value `helper.conf` is assumed.
CLI options:
| Flag name | Description |
|---------------------------------|---------------------------------------------------------------------|
| `-config` | Path to the configuration file |
| `-help` | Print interactive help |
| `-daemon-mode={true\|false}` | Boolean true or false. Overrides `daemon_mode` in the config file. |
## Configuration
The configuration file is an [HCL](https://github.com/hashicorp/hcl) formatted file that defines the following configurations:
| Configuration | Description | Example Value |
|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `agent_address` | Socket address of SPIRE Agent. | `"/tmp/agent.sock"` |
| `cmd` | The path to the process to launch and monitor and signal for certificate renewals. Ignored if `daemon_mode=false` | `"ghostunnel"` |
| `cmd_args` | The arguments of the process to launch. Split by spaces into an argument vector. | `"server --listen localhost:8002 --target localhost:8001--keystore certs/svid_key.pem --cacert certs/svid_bundle.pem --allow-uri-san spiffe://example.org/Database"` |
| `pid_file_name` | Path to a file containing a process ID to signal when certificates are renewed. Not required when using 'cmd'. | `"/var/run/ghostunnel.pid"` |
| `cert_dir` | Directory name to store the fetched certificates. This directory must be created previously. | `"certs"` |
| `daemon_mode` | Toggle running as a daemon, keeping X.509 and JWT up to date; or just fetch X.509 and JWT and exit 0. Does not background itself. | `true` |
| `add_intermediates_to_bundle` | Add intermediate certificates into Bundle file instead of SVID file. | `true` |
| `renew_signal` | The signal that the process to be launched expects to reload the certificates. It is not supported on Windows. | `"SIGUSR1"` |
| `svid_file_name` | File name to be used to store the X.509 SVID public certificate in PEM format. | `"svid.pem"` |
| `svid_key_file_name` | File name to be used to store the X.509 SVID private key and public certificate in PEM format. | `"svid_key.pem"` |
| `svid_bundle_file_name` | File name to be used to store the X.509 SVID Bundle in PEM format. | `"svid_bundle.pem"` |
| `jwt_svids` | An array with the audience, optional extra audiences array, and file name to store the JWT SVIDs. File is Base64-encoded string). | `[{jwt_audience="your-audience", jwt_extra_audiences=["your-extra-audience-1", "your-extra-audience-2"], jwt_svid_file_name="jwt_svid.token"}]` |
| `jwt_bundle_file_name` | File name to be used to store JWT Bundle in JSON format. | `"jwt_bundle.json"` |
| `include_federated_domains` | Include trust domains from federated servers in the CA bundle. | `true` |
| `cert_file_mode` | The octal file mode to use when saving the X.509 public certificate file. | `0644` |
| `key_file_mode` | The octal file mode to use when saving the X.509 private key file. | `0600` |
| `jwt_bundle_file_mode` | The octal file mode to use when saving a JWT Bundle file. | `0600` |
| `jwt_svid_file_mode` | The octal file mode to use when saving a JWT SVID file. | `0600` |
| `hint` | Hint to use to pick the SPIFFE ID. | `` |
**Notes**:
* If `cmd` is specified, spiffe-helper will connect its `stdin`, `stdout` and
`stderr` to that of the command it invokes. If this is not desired, close
these file descriptors before invoking spiffe-helper.
### Health Checks Configuration
SPIFFE Helper can expose and endpoint that can be used for health checking
| Configuration | Description | Example Value |
|----------------------------------|----------------------------------------------------------------------------------------------------------------------|---------------|
| `health_checks.listener_enabled` | Whether to start an HTTP server at the configured endpoint for the daemon health. Doesn't apply for non-daemon mode. | `false` |
| `health_checks.bind_port` | The port to run the HTTP health server. | `8081` |
| `health_checks.liveness_path` | The URL path for the liveness health check | `/live` |
| `health_checks.readiness_path` | The URL path for the readiness health check | `/ready` |
### Operating modes and configuration details
spiffe-helper has two primary operating modes - "daemon mode" (the default),
where it runs continuously and manages the certificates, and "non-daemon mode",
where it fetches the certificates once and exits.
The helper can be used in several ways, as detailed below:
* Signal an external process when the certificates are renewed.
* Run a command that reloads an external process when the certificates are renewed.
* Run a command that uses the certificates, and signal it when they are renewed
(not recommended)
* Fetch the certificates once and exit.
Note that "daemon mode" does not actually detach itself from the controlling
process and background itself like a unix "daemon". It just keeps running until
terminated by a signal or a fatal error.
`spiffe-helper` does not have all the features of a proper process supervisor,
so it's usually best to let a dedicated process supervisor like systemd manage
the process that uses the certificates. Use `spiffe-helper` to fetch and renew
the certificates and wake the external process via `cmd` or `pid_file_name`
when the certificates are reloaded.
#### Use in daemon-mode with file watcher
If the process using the certificates can watch the on-disk files for changes,
spiffe-helper can be run in `daemon_mode` with no `cmd` or `pid_file_name`. It
will fetch and renew the certificates, overwrite them on disk, and the process
will pick up the changes.
This approach is recommended where possible.
#### Use in daemon-mode with `cmd` to run a process or a reload command
`cmd` and `cmd_args` are used in `daemon_mode` to run a command whenever the
certificates are renewed. This can be a long-lived process that uses the
certificates, or a short-lived command that signals a reload mechanism
for an externally-managed process.
:warning: **cmd_args is not parsed according to shell-like rules**. The
`cmd_args` will be split into individual arguments using space separation
unless the argument is enclosed in double quotes, which are consumed. Double
quotes must be backslash escaped in the hcl string. For example:
```hcl
cmd_args = "\"this is one argument\""
```
Double quotes within the argument string must be escaped by doubling them so
they are not interpreted as argument delimiters. E.g.:
```hcl
cmd_args = "\"this is a single argument with ONE double-quote \"\" in it\""
```
Single quotes are NOT respected for argument quoting, and do not protect double
quotes. For example:
```hcl
cmd = "sh"
cmd_args = "-c 'echo hello world'"
```
will run `sh` with the argument-vector ["-c", "'echo", "hello", "world'"], not
["-c", "echo hello world"], which will fail with `Syntax error: Unterminated
quoted string`.
`cmd_args` is *not* subject to shell metacharacter expansion or interpretation.
If you need to use shell features, you must invoke a shell explicitly, e.g.
`cmd = "/bin/sh"` and `cmd_args = "-c \"echo hello\""`. Be careful with shell
invocations, as they can introduce security vulnerabilities and should be
avoided where possible.
The command's stdout and stderr will be attached to spiffe-helper's stdout
and stderr. Its stdin will be closed.
The process specified by `cmd` and `cmd_args` will not be launched for the
first time until the certificates are fetched successfully.
`spiffe-helper` continues running if the process created by `cmd` exits. The
process is not re-launched immediately if it exits.
If the process is still running next time the certs are renewed,
`spiffe-helper` will signal it with `renew_signal`. If it has exited,
`spiffe-helper` will re-launch it instead. This can be used to manage
certificate reloading in externally-managed processes that do not support
reloading certificates with a signal.
#### Use in daemon-mode with `pid_file_name` to signal an externally-managed process
If running in `daemon_mode` with `pid_file_name` set, the pid in
`pid_file_name` is sent the signal `renew_signal` to reload the certificates
when they are renewed.
`pid_file_name` is re-read every time the process is to be signaled, so it can
be updated with a new pid if the process changes.
An error will be logged if the pid file cannot be opened, read, or the value
parsed, and the attempt to signal the process will be skipped. The process will
still be signalled next time the certificates are renewed.
#### Combining `cmd` and `pid_file_name`
Both `cmd` and `pid_file_name` can be used at the same time. `spiffe-helper` will
both run the specified command and signal the process in the pid file. This can be
useful to use `cmd` to start the process to be managed, and `pid_file_name` to signal
a reload mechanism that is not signal-based.
#### Use in one-shot non-daemon mode
If `daemon_mode` is false, `spiffe-helper` will fetch the certificates once and
exit. This can be useful for one-shot scripts or for use in a process supervisor
that does not require a long-lived process.
`cmd` and `pid_file_name` are ignored in non-daemon mode. No command will be
run and no signals will be sent. They may be disallowed in future.
`spiffe-helper` cannot be used as a transparent wrapper around another
command because it does not forward stdin, signals, file descriptors, exit
when the child process exits, or return the managed process's exit code as
its own exit code. Instead, consider running the other process separately,
under the control of a proper process supervisor like systemd, and signaling
it via `pid_file_name`.
:warning: A future release may support running a command and/or signalling an
external process in non-daemon mode, so it is recommended to leave `cmd`,
`renew_signal` and `pid_file_name` blank if `daemon_mode` is false.
### Configuration example
```
agent_address = "/tmp/spire-agent/public/api.sock"
cmd = "ghostunnel"
cmd_args = "server --listen localhost:8002 --target localhost:8001 --keystore certs/svid_key.pem --cacert certs/svid_bundle.pem --allow-uri-san spiffe://example.org/Database"
cert_dir = "certs"
renew_signal = "SIGUSR1"
svid_file_name = "svid.pem"
svid_key_file_name = "svid_key.pem"
svid_bundle_file_name = "svid_bundle.pem"
jwt_svids = [{jwt_audience="your-audience",jwt_extra_audiences=["your-extra-audience-1", "your-extra-audience-2"], jwt_svid_file_name="jwt_svid.token"}]
jwt_bundle_file_name = "bundle.json"
cert_file_mode = 0444
key_file_mode = 0444
jwt_bundle_file_mode = 0444
jwt_svid_file_mode = 0444
```
### Windows example
```
agent_address = "spire-agent\\public\\api"
cert_dir = "certs"
svid_file_name = "svid.pem"
svid_key_file_name = "svid_key.pem"
svid_bundle_file_name = "svid_bundle.pem"
jwt_svids = [{jwt_audience="your-audience",jwt_extra_audiences=["your-extra-audience-1", "your-extra-audience-2"], jwt_svid_file_name="jwt_svid.token"}]
jwt_bundle_file_name = "bundle.json"
```
## Development and testing
This is a pretty straightforward Go project. You can use the standard Go tools
to build and test it.
Please run the tests for Windows for your PRs. `wine` is sufficient if you
don't have a convenient Windows machine or VM, and you don't need the Windows
Go SDK to cross-compile the test suite and run it. Install `wine` with
`sudo apt-get install wine` or similar, then run the tests with `make test-wine`.