community.general.java_keystore module – Create a Java keystore in JKS format
Note
This module is part of the community.general collection (version 10.7.5).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install community.general.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: community.general.java_keystore.
Synopsis
- Bundle a x509 certificate and its private key into a Java Keystore in JKS format. 
Requirements
The below requirements are needed on the host that executes this module.
- openssl in PATH (when - ssl_backend=openssl)
- keytool in PATH 
- cryptography >= 3.0 (when - ssl_backend=cryptography)
Parameters
| Parameter | Comments | 
|---|---|
| The attributes the resulting filesystem object should have. To get supported flags look at the man page for  This string should contain the attributes in the same order as the one displayed by  The  | |
| Content of the certificate used to create the keystore. If the fingerprint of the provided certificate does not match the fingerprint of the certificate bundled in the keystore, the keystore is regenerated with the provided certificate. Exactly one of  | |
| Location of the certificate used to create the keystore. If the fingerprint of the provided certificate does not match the fingerprint of the certificate bundled in the keystore, the keystore is regenerated with the provided certificate. Exactly one of  | |
| Absolute path of the generated keystore. | |
| Keystore is created even if it already exists. Choices: 
 | |
| Name of the group that should own jks file. | |
| Type of the Java keystore. When this option is omitted and the keystore does not already exist, the behavior follows  When this option is omitted and the keystore already exists, the current type is left untouched, unless another option leads to overwrite the keystore (in that case, this option behaves like for keystore creation). When  Choices: 
 | |
| Mode the file should be. | |
| Name of the certificate in the keystore. If the provided name does not exist in the keystore, the module will re-create the keystore. This behavior changed in community.general 3.0.0, before that the module would fail when the name did not match. | |
| Name of the user that should own jks file. | |
| Password that should be used to secure the keystore. If the provided password fails to unlock the keystore, the module will re-create the keystore with the new passphrase. This behavior changed in community.general 3.0.0, before that the module would fail when the password did not match. | |
| Content of the private key used to create the keystore. Exactly one of  | |
| Passphrase used to read the private key, if required. | |
| Location of the private key used to create the keystore. Exactly one of  | |
| The level part of the SELinux filesystem object context. This is the MLS/MCS attribute, sometimes known as the  When set to  | |
| The role part of the SELinux filesystem object context. When set to  | |
| The type part of the SELinux filesystem object context. When set to  | |
| The user part of the SELinux filesystem object context. By default it uses the  When set to  | |
| Backend for loading private keys and certificates. Choices: 
 | |
| Influence when to use atomic operation to prevent data corruption or inconsistent reads from the target filesystem object. By default this module uses atomic operations to prevent data corruption or inconsistent reads from the target filesystem objects, but sometimes systems are configured or just broken in ways that prevent this. One example is docker mounted filesystem objects, which cannot be updated atomically from inside the container and can only be written in an unsafe manner. This option allows Ansible to fall back to unsafe methods of updating filesystem objects when atomic operations fail (however, it doesn’t force Ansible to perform unsafe writes). IMPORTANT! Unsafe writes are subject to race conditions and can lead to data corruption. Choices: 
 | 
Attributes
| Attribute | Support | Description | 
|---|---|---|
| Support: full | Can run in  | |
| Support: none | Will return details on what has changed (or possibly needs changing in  | 
Notes
Note
- certificateand- private_keyrequire that their contents are available on the controller (either inline in a playbook, or with the ansible.builtin.file lookup), while- certificate_pathand- private_key_pathrequire that the files are available on the target host.
- By design, any change of a value of options - keystore_type,- nameor- password, as well as changes of key or certificate materials will cause the existing- destto be overwritten.
See Also
See also
- community.crypto.openssl_pkcs12
- Generate OpenSSL PKCS#12 archive. 
- community.general.java_cert
- Uses keytool to import/remove certificate to/from java keystore (cacerts). 
Examples
- name: Create a keystore for the given certificate/private key pair (inline)
  community.general.java_keystore:
    name: example
    certificate: |
      -----BEGIN CERTIFICATE-----
      h19dUZ2co2f...
      -----END CERTIFICATE-----
    private_key: |
      -----BEGIN RSA PRIVATE KEY-----
      DBVFTEVDVFJ...
      -----END RSA PRIVATE KEY-----
    password: changeit
    dest: /etc/security/keystore.jks
- name: Create a keystore for the given certificate/private key pair (with files on controller)
  community.general.java_keystore:
    name: example
    certificate: "{{ lookup('file', '/path/to/certificate.crt') }}"
    private_key: "{{ lookup('file', '/path/to/private.key') }}"
    password: changeit
    dest: /etc/security/keystore.jks
- name: Create a keystore for the given certificate/private key pair (with files on target host)
  community.general.java_keystore:
    name: snakeoil
    certificate_path: /etc/ssl/certs/ssl-cert-snakeoil.pem
    private_key_path: /etc/ssl/private/ssl-cert-snakeoil.key
    password: changeit
    dest: /etc/security/keystore.jks
Return Values
Common return values are documented here, the following are the fields unique to this module:
| Key | Description | 
|---|---|
| Executed command to get action done. Returned: changed and failure Sample:  | |
| Output from stderr of keytool/openssl command after error of given command. Returned: failure Sample:  | 
