Authority Provider v2
Overview
Authority Provider v3
Overview
Authority Provider Legacy
Authority Provider Legacy is deprecated and will be removed in future release.
Compliance Provider v2
Overview
Compliance Provider
Overview
Credential Provider
Overview
Cryptography Provider v2
Overview
Cryptography Provider v1
Cryptography Provider v1 is deprecated since 2.20.0. New connectors implement Cryptography Provider v2, the default interface. Core keeps serving v1 for the tokens bound to it.
Discovery Provider v2
Overview
Discovery Provider
This page describes the v1 Discovery Provider, which discovers certificates. Discovery Provider v2 discovers certificates and keys, collects results while a run is in progress, and supports stopping, resuming and cancelling a run.
Entity Provider
Entity Provider helps to integrate any technology (open and proprietary) that is not able, not capable, or you do not want to, use standard interface and protocols for management and automation of the certificate and cryptographic keys lifecycle.
Notification Provider
Notification Provider provides interface to extend the notification features of the platform. Notification Provider can be used to send notifications to the users of the platform using email, SMS, Slack, Team, webhook, or any other technology.
Structured Certificate Request Content
This page describes the wire contract for the typed certificate request content in Authority Provider v3. It is written for connector developers. For the platform-side model — request attributes, field mappings, and set resolution — see Request Attribute and the contributor page Request Attributes.
Secret Provider
The Secret Provider is a provider interface responsible for fetching and managing secrets from various secret management systems. It abstracts the underlying implementation details and provides a consistent API for accessing secrets.
Signature Formatting Provider
The Signature Formatting Provider is a connector interface responsible for assembling the data structures involved in a signing operation — building the exact bytes that Core must sign, and reconstituting the finished signed object once the signature is available. It holds no keys and performs no cryptographic signing itself; that stays with Core.