Ansible Vars for PAM Automation

The vars file is one of three input files needed to deploy PAM with Ansible:

The vars file is a YAML file typically named mypam.vars or other similar name. The PAM CDM package includes an example vars file example.vars that may be used as a template or starting point.

The vars file is unencrypted and should only be used to store non-secret input values. Secret input values should be stored in the vault file instead.

Passing Vars to Ansible Playbooks

The vars file should be formatted as a simple YAML dictionary of name/value pairs:

name1: value1
name2: value2
name3: value3

Vars may be set individually on the ansible-playbook command line:

ansible-playbook -e name1=value1 -e name2=value2 -e name3=value3

But it is often more convenient to pass a vars file instead:

  ansible-playbook -e @mypam.vars

Supported Vars for Ansible PAM Deployments

The following vars are recognized by the PAM deployment playbooks. Both secret and non-secret vars are included. Variables marked secret should stored in the vault file, not the vars file.

Some vars are required, some are optional, and some are only needed for specific PAM deployment scenarios. The recommended process is to go through the list and decide if your PAM deployment needs each variable. If so, set the variable in your vars file (or vault file if it is a secret).

ansible_linux_username

ansible_linux_password (secret)

pam_admin_username

pam_admin_password (secret)

pam_crypt_password (secret)

pam_database_type

pam_database_server

pam_database_username

pam_database_password (secret)

pam_frontend_hostname

pam_frontend_port

pam_install_folder

pam_ldap_server

pam_ldap_user

pam_ldap_password (secret)

pam_master_password (secret)