The integration runs over HTTPS against the CryptoHub REST API, so it places no operating system requirement on the AppViewX host beyond what AppViewX itself requires. No Futurex client library is installed on the AppViewX host.
This integration applies to AppViewX AVX ONE certificate lifecycle management — the CERT+ / CLM module and its Automation Workflow engine. It relies on capabilities that are standard across current AVX ONE and AppViewX CERT+ releases (SaaS or self-managed): certificate lifecycle management, visual automation workflows, and outbound REST/HTTP connector calls for external key generation. No specific minimum AppViewX version is required.
Create the following before you configure AppViewX. Prepare CryptoHub covers each one.
The AppViewX service deployed in CryptoHub, with an endpoint. The endpoint provides the identity and credentials AppViewX authenticates with, its permissions, and its Host API command authorization.
Allow outbound HTTPS from the AppViewX host to the CryptoHub REST API, specified by FQDN (for example, cryptohub.example.com) or CIDR (for example, 10.0.0.0/24).
Allow outbound access from AppViewX to your certificate authority.
Ensure DNS resolution is available for the CryptoHub address from the AppViewX host.
TLS inspection or SSL proxies can break the TLS session to the CryptoHub REST API. Exempt the CryptoHub FQDN(s) from inspection. Configure the CryptoHub with a FQDN so the exemption applies.
This guide documents RSA key generation. Use a modulus size your certificate authority accepts, such as 2048 or 4096, and confirm the size satisfies the certificate template or issuance policy you enroll against.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.