This is a example for ansible as CA in a PKI.

That is the CA tree, that is created by the Ansible-Playbook:

As staging variation with 4 VMs	And as production variation with 7 VMs

The staging variation is in the inventory directory inventories/staging and the production variation is in the inventory directory inventories/production

That is the work flow of the certification:

Certificate and csr will be exchange over http (nginx)

This is the proposal how the Ansible-PKI can be embedded in a sign certificates process.

Has the variable debug_output in the file group_vars/pki.yml the value true, you get a lot of output.

The Playbook git_check.yml is only a example for checking the integrity of the git code.

For the most of the inventory (directory) you find only links between the tiers. The goal is reduction the redundancies.

The differences are:

• inventories/production/group_vars/pki.yml
• inventories/production/group_vars/pki_azure_deploy.yml

$ diff ./inventories/staging/group_vars/pki.yml  ./inventories/production/group_vars/pki.yml

6,9c6,12
< vm_01:                      "51.116.225.106"
< vm_02:                      "51.116.114.242"
< vm_03:                      "51.116.114.249"
< vm_04:                      "51.116.115.5"
---
> vm_01:                      "20.52.41.243"
> vm_02:                      "20.52.41.152"
> vm_03:                      "20.52.41.88"
> vm_04:                      "20.52.41.223"
> vm_05:                      "51.116.186.241"
> vm_06:                      "51.116.187.148"
> vm_07:                      "20.52.41.92"
13,21c16,24
< policy_ca_staff_ip:         "{{ vm_01 }}"
< policy_ca_service_ip:       "{{ vm_01 }}"
< issue_ca_staff_ip:          "{{ vm_02 }}"
< issue_ca_service_ip:        "{{ vm_03 }}"
< foo_dum_my_ip:              "{{ vm_04 }}"
< bar_dum_my_ip:              "{{ vm_04 }}"
< baz_dum_my_ip:              "{{ vm_04 }}"
< jane_doe_ip:                "{{ vm_02 }}"
< john_doe_ip:                "{{ vm_02 }}"
---
> policy_ca_staff_ip:         "{{ vm_02 }}"
> policy_ca_service_ip:       "{{ vm_03 }}"
> issue_ca_staff_ip:          "{{ vm_04 }}"
> issue_ca_service_ip:        "{{ vm_05 }}"
> jane_doe_ip:                "{{ vm_06 }}"
> john_doe_ip:                "{{ vm_06 }}"
> foo_dum_my_ip:              "{{ vm_07 }}"
> bar_dum_my_ip:              "{{ vm_07 }}"
> baz_dum_my_ip:              "{{ vm_07 }}"
27d29

The differences is, that production use more VMs as staging.

Preparation: Edit the host_vars file and change the IPs of the VMs (in group_vars/pki.yml). And maybe the ansible user in the file pki.yml in the group_vars.

For run this example enter (this runs about 15 minutes):

export ANSIBLE_HOST_KEY_CHECKING=False && \
ansible-playbook \
-i ./inventories/staging/hosts.yml \
./pki_bootstrap.yml

Here you can find a Detailed documentation in german and down load as...

• eBook
• MS Doc
• OpenDocument
• PDF

• The playbook is switched off selinux. But for an effect, ths need a restart of the virtual machine.
• Some times under Ubuntu: The step "TASK [pre_config : Upgrade all apt packages]" hangs up. Solution: Restart the playbook.
• Terraform print: resource with the ID "XXX" already exists - to be managed via Terraform this resource needs to be imported into the State. Solution: remove the .tmp directory.

• kleopatra
• Xca
• draw.io

• golinuxcloud.com
• wikipedia.org to X.509
• openssl cookbook
• openssl man page

• Try playbook with OpenSUSE
• OpenSSL Issue: "Write out database with 1 new entries \ Segmentation fault (core dumped)"
• Adding a root CA offline mode to jump over the CAs thats a offline.

• RabbitMQ
• PKI as JavaScript lib
• Sharkey is a service for managing certificates for use by OpenSSH (Writen in Go)