Writing Adaptable Drivers¶
Venafi Adaptable Drivers provide a way quick, easy framework to build solutions, primarily with target application platforms (web servers, network devices, application firewalls, etc.) and CAs (certificate authorities), but also to support flexible workflow and logging needs for unique environments.
Note
Venafi Adaptable Drivers support Venafi TLS Protect Datacenter only. For information about building an integration with Venafi TLS Protect Cloud, please see the Connector Framework documentation on Venafi Dev Central for Machine Connectors and CA Connectors.
Getting Started¶
- Read through this section on the Adaptable Framework (You're almost done!)
- Decide which DevKit you'll need below
- Build & test your driver using the tools provided in the DevKit
- Test your driver against TLS Protect Datacenter
-
Submit your driver to Cool Solutions (Venafi's managed GitLab instance)
Note
You will need a Venafi user account in order to access..
-
Complete the Marketplace Listing Questionnaire
Adaptable Driver Types¶
Choose this if you are building a solution between Venafi and a Machine Identity Producer, like a Certificate Authority or Managed PKI.
Choose this if you are building a solution between Venafi and a Machine Identity Consumer, like an application server, network device, WAF, etc.
Choose this if you are building a solution that will be used to perform virtually any programmatic task in response to the logging of a Venafi event.
Choose this if you are building a solution with the goal of further customizing Venafi's native approval workflows.
This use case is similar to the "Adaptable App." The main difference is "Bulk Provisioning" was designed to provision many machine identities to a target using as few API calls as possible. Choose this if you are building a solution between Venafi and a Machine Identity Consumer, like a NGFW, traffic inspection device, or something else that needs many certificates with few connections to the target device.