This is a collection of Ansible playbooks to use with EJBCA, SignServer, and integrations. Both Community and Enterprise versions of EJBCA are supported. By using these Ansible playbooks you can easily get EJBCA or SignServer up and running, including a complete technology stack with Java 11, Apache HTTPD, Maria DB, SoftHSM, and Wildfly.

These playbooks are available:

• ansible_ejbca_signsrv - For use with EJBCA & SignServer Community or Enterprise version to install and configure EJBCA CA, external RA, & external VA, or only standalone CA without deploying external RA/VA, and SignServer.
• ejbca_certificate_request_role - For use with EJBCA Enterprise version to issue certificates from an EJBCA server using the REST API

For details on how to set up and run the Ansible playbooks, see README in the respective playbook:

• Ansible EJBCA SignServer README
• EJBCA Certificate Request Role README

For more information, see

• Ansible EJBCA SignServer Requirements
• EJBCA Certificate Request Role Requirements

In the Keyfactor Community, we welcome contributions.

The Community software is open-source and community-supported, meaning that no SLA is applicable.

• Read more in our documentation: Deploying PKI and signature services in DevOps environments
• Ask the community for ideas: EJBCA Ansible Playbook Discussions
• To report a problem or suggest a new feature, go to Issues.
• If you want to contribute actual bug fixes or proposed enhancements, see the Contributing Guidelines and go to Pull requests.

Commercial support is available for EJBCA Enterprise and SignServer Enterprise.

For license information, see LICENSE.

See all Keyfactor EJBCA GitHub projects or Keyfactor SignServer GitHub projects.