mirror of
https://github.com/netzbegruenung/passbolt-salt
synced 2024-05-01 20:14:52 +02:00
75 lines
3 KiB
Markdown
75 lines
3 KiB
Markdown
# About
|
|
This Python module allows you to manage secrets for Saltstack via Passbolt. This makes managing secrets easier than manually encrypting them and storing the encrpyted password in the Saltstack repository.
|
|
|
|
Additionally, it is possible to only have one source of truth for passwords for users and IT infrastructure while being able to manage access for each password. That means that all users can contribute to the Saltack configuration and manage (view/add/change) secrets within their responsibility.
|
|
|
|
# License
|
|
[MIT](LICENSE)
|
|
|
|
# Production Setup
|
|
|
|
1. Go to your Salt master and install the module with `salt-pip`
|
|
|
|
```shell
|
|
salt-pip install passbolt-salt
|
|
```
|
|
|
|
This will install this module and its dependencies.
|
|
|
|
3. Create a Passbolt account for the Salt master.
|
|
|
|
4. Copy the private and public PGP key files to `/etc/salt`.
|
|
|
|
5. Import the new Passbolt private key on the Salt master:
|
|
```shell
|
|
gpg --import /etc/salt/passbolt_private.asc
|
|
```
|
|
|
|
6. Create a `/etc/salt/passbolt.ini` file with the following content:
|
|
```ini
|
|
[PASSBOLT]
|
|
SERVER = https://passbolt.example.com
|
|
#SERVER_PUBLIC_KEY_FILE = <optional: server_public.asc>
|
|
USER_FINGERPRINT = [REPLACE WITH GPG KEY FINGERPRINT]
|
|
USER_PUBLIC_KEY_FILE = /etc/salt/passbolt_public.asc
|
|
USER_PRIVATE_KEY_FILE = /etc/salt/passbolt_private.asc
|
|
PASSPHRASE = [REPLACE WITH PASSBOLT USER PASSWORD]
|
|
```
|
|
|
|
7. Change file permissions:
|
|
```shell
|
|
chown salt /etc/salt/passbolt*
|
|
chmod 600 /etc/salt/passbolt*
|
|
```
|
|
|
|
# Use Passwords of Passbolt Group in Pillar
|
|
Look into the [example](example) directory to see how the integration is done.
|
|
|
|
1. Create Pillar sls files for the different Salt minions, insert the content below and replace the group UUID.
|
|
```python
|
|
#!py
|
|
def run():
|
|
from salt_passbolt import fetch_passbolt_passwords
|
|
return fetch_passbolt_passwords("27b9abd4-af9b-4c9e-9af1-cf8cb963680c")
|
|
```
|
|
Hint: you can find the group UUID in the URL of the Passbolt admin interface when editing a group.
|
|
|
|
2. In a state, reference secrets with their UUID. See the `example/salt/important_secrets/files/secret.conf`.
|
|
```
|
|
password={{ pillar['passbolt']['3ec2a739-8e51-4c67-89fb-4bbfe9147e17'] }}
|
|
```
|
|
Hint: you can find the secret UUID in the URL of your browser by clicking on the checkbox of a secret.
|
|
|
|
# Performance
|
|
All passwords are decrypted with a single process (gpg-agent). If many minions need to access their Pillar at the same time, the gpg-agent becomes a bottleneck. To avoid this bottleneck, the Pillar cache can be enabled for the Salt master with `pillar_cache: True`. The following crontab entry updates the Pillar cache twice a day:
|
|
```
|
|
0 */12 * * * rm -rf /var/cache/salt/master/pillar_cache/* && salt '*' -b1 pillar.items
|
|
```
|
|
|
|
# YAML Replacement Structure
|
|
If the Passbolt server is not available, for example during local development, a file with the following format can replace the Python code mentioned in step 8:
|
|
```yaml
|
|
passbolt:
|
|
3ec2a739-8e51-4c67-89fb-4bbfe9147e17: MY_SECRET
|
|
```
|