mirror of
https://github.com/freeipa/ansible-freeipa.git
synced 2026-06-09 18:25:53 +00:00
c236fe3d62
IPA CLI allows the creation of vaults without specifying user, service or a shared vault, defaulting to create a user vault for the `admin` user. The vault module, required that one of user, service or shared was explicitly provided, and this patch makes the module behave like the CLI command. Tests were added to reflect this change.
204 lines
4.5 KiB
Markdown
204 lines
4.5 KiB
Markdown
Vault module
|
|
===================
|
|
|
|
Description
|
|
-----------
|
|
|
|
The vault module allows to ensure presence and absence of vault and members of vaults.
|
|
|
|
The vault module is as compatible as possible to the Ansible upstream `ipa_vault` module, and additionally offers to make sure that vault members, groups and owners are present or absent in a vault, and allow the archival of data in vaults.
|
|
|
|
|
|
Features
|
|
--------
|
|
* Vault management
|
|
|
|
|
|
Supported FreeIPA Versions
|
|
--------------------------
|
|
|
|
FreeIPA versions 4.4.0 and up are supported by the ipavault module.
|
|
|
|
|
|
Requirements
|
|
------------
|
|
|
|
**Controller**
|
|
* Ansible version: 2.8+
|
|
|
|
**Node**
|
|
* Supported FreeIPA version (see above)
|
|
* KRA service must be enabled
|
|
|
|
|
|
Usage
|
|
=====
|
|
|
|
Example inventory file
|
|
|
|
```ini
|
|
[ipaserver]
|
|
ipaserver.test.local
|
|
```
|
|
|
|
Example playbook to make sure vault is present:
|
|
|
|
```yaml
|
|
---
|
|
- name: Playbook to handle vaults
|
|
hosts: ipaserver
|
|
become: true
|
|
|
|
tasks:
|
|
- ipavault:
|
|
ipaadmin_password: SomeADMINpassword
|
|
name: symvault
|
|
username: admin
|
|
vault_password: MyVaultPassword123
|
|
description: A standard private vault.
|
|
```
|
|
|
|
Example playbook to make sure that a vault and its members are present:
|
|
|
|
```yaml
|
|
---
|
|
- name: Playbook to handle vaults
|
|
hosts: ipaserver
|
|
become: true
|
|
|
|
tasks:
|
|
- ipavault:
|
|
ipaadmin_password: SomeADMINpassword
|
|
name: symvault
|
|
username: admin
|
|
users: user01
|
|
```
|
|
|
|
`action` controls if the vault, data, member or owner will be handled. To add or remove members or vault data, set `action` to `member`.
|
|
|
|
Example playbook to make sure that a vault member is present in vault:
|
|
|
|
```yaml
|
|
---
|
|
- name: Playbook to handle vaults
|
|
hosts: ipaserver
|
|
become: true
|
|
|
|
tasks:
|
|
- ipavault:
|
|
ipaadmin_password: SomeADMINpassword
|
|
name: symvault
|
|
username: admin
|
|
users: user01
|
|
action: member
|
|
```
|
|
|
|
Example playbook to make sure that a vault owner is absent in vault:
|
|
|
|
```yaml
|
|
---
|
|
- name: Playbook to handle vaults
|
|
hosts: ipaserver
|
|
become: true
|
|
|
|
tasks:
|
|
- ipavault:
|
|
ipaadmin_password: SomeADMINpassword
|
|
name: symvault
|
|
username: admin
|
|
owner: user01
|
|
action: member
|
|
state: absent
|
|
```
|
|
|
|
Example playbook to make sure vault data is present in a symmetric vault:
|
|
|
|
```yaml
|
|
---
|
|
- name: Playbook to handle vaults
|
|
hosts: ipaserver
|
|
become: true
|
|
|
|
tasks:
|
|
- ipavault:
|
|
ipaadmin_password: SomeADMINpassword
|
|
name: symvault
|
|
username: admin
|
|
vault_password: MyVaultPassword123
|
|
vault_data: >
|
|
Data archived.
|
|
More data archived.
|
|
action: member
|
|
```
|
|
|
|
Example playbook to make sure vault data is absent in a symmetric vault:
|
|
|
|
```yaml
|
|
---
|
|
- name: Playbook to handle vaults
|
|
hosts: ipaserver
|
|
become: true
|
|
|
|
tasks:
|
|
- ipavault:
|
|
ipaadmin_password: SomeADMINpassword
|
|
name: symvault
|
|
username: admin
|
|
vault_password: MyVaultPassword123
|
|
action: member
|
|
state: absent
|
|
```
|
|
|
|
Example playbook to make sure vault is absent:
|
|
|
|
```yaml
|
|
---
|
|
- name: Playbook to handle vaults
|
|
hosts: ipaserver
|
|
become: true
|
|
|
|
tasks:
|
|
- ipavault:
|
|
ipaadmin_password: SomeADMINpassword
|
|
name: symvault
|
|
username: admin
|
|
state: absent
|
|
```
|
|
|
|
Variables
|
|
=========
|
|
|
|
ipavault
|
|
-------
|
|
|
|
Variable | Description | Required
|
|
-------- | ----------- | --------
|
|
`ipaadmin_principal` | The admin principal is a string and defaults to `admin` | no
|
|
`ipaadmin_password` | The admin password is a string and is required if there is no admin ticket available on the node | no
|
|
`name` \| `cn` | The list of vault name strings. | yes
|
|
`description` | The vault description string. | no
|
|
`nomembers` | Suppress processing of membership attributes. (bool) | no
|
|
`vault_public_key` \| `ipavaultpublickey` | Vault public key. | no
|
|
`vault_salt` \| `ipavaultsalt` | Vault salt. | no
|
|
`vault_type` \| `ipavaulttype` | Vault types are based on security level. It can be one of `standard`, `symmetric` or `asymmetric`, default: `symmetric` | no
|
|
`user` \| `username` | Any user can own one or more user vaults. | no
|
|
`service` | Any service can own one or more service vaults. | no
|
|
`shared` | Vault is shared. Default to false. (bool) | no
|
|
`users` | Users that are members of the vault. | no
|
|
`groups` | Groups that are member of the vault. | no
|
|
`vault_data` \| `ipavaultdata` | Data to be stored in the vault. | no
|
|
`action` | Work on vault or member level. It can be on of `member` or `vault` and defaults to `vault`. | no
|
|
`state` | The state to ensure. It can be one of `present` or `absent`, default: `present`. | no
|
|
|
|
|
|
Notes
|
|
=====
|
|
|
|
ipavault uses a client context to execute, and it might affect execution time.
|
|
|
|
|
|
Authors
|
|
=======
|
|
|
|
Rafael Jeffman
|