Vendor identities use a dedicated portal rather than the administrator UI.
Let approved third parties request and manage the certificates they are responsible for without giving them access to the main SSLNexus administration plane.
Vendors often need certificates for systems they operate on behalf of an organisation. Emailing CSRs, private keys or renewal reminders between teams creates unnecessary risk and delay. A dedicated workflow keeps vendor access separate and auditable.
Vendor identities use a dedicated portal rather than the administrator UI.
Restrict vendors by domain and approved source ranges.
CSR key generation occurs in the vendor browser so the private key does not enter SSLNexus infrastructure.
SSLNexus is installed into customer infrastructure and is designed to keep certificate operations, target access and private-key custody under customer control. The platform coordinates lifecycle work without requiring the estate to be rebuilt around a vendor-hosted key store.
No. Vendor Portal authentication and capabilities are separated from Client Server administration.
No. Browser-local generation keeps the private key out of the Client Server API.
Vendor registry and organisation mapping are designed to support controlled onboarding and offboarding.