Before you start - Futurex Documentation

Overview

Certificate Authority

Cloud key management

Code signing

Credential management

Certificate management

Data protection

Data storage

Database

Endpoint management

DNS

Generic

IT automation and orchestration

Key management

Privileged access management

Secrets management

Secure printing

SSH

Virtualization

VPN

Verify your environment meets these requirements.

Supported hardware

KMES Series 3, application version 6.3.1.3 or later, with initial setup completed (including loading a Platform Master Key and network configuration).

Supported operating systems

This integration guide uses the Web application ARchive (WAR) file version of Jenkins. You can install it on any operating system or platform that runs a version of Java supported by Jenkins. See the Java Requirements page on the jenkins.io website for details.

Required access

An account on the KMES with administrator permissions to create roles, identities, TLS PKI, and update system settings.
Local administrator/root access on the server where Jenkins is installed.

Network and firewall

Allow outbound TCP port2001(default Host API port) from the Jenkins server to the KMES Series 3, specified by FQDN (for example, kmes.example.com) or CIDR (for example, 10.0.0.0/24).

TLS inspection or SSL proxies can break mutual TLS handshakes. Exempt the KMES FQDN(s) from inspection. Configure the KMES Series 3 with an FQDN so the exemption applies.