---
title: "Publish a certificate"
slug: "certificates-flow-how-to-publish-a-certificate"
updated: 2026-11-03T14:47:50Z
published: 2026-11-03T14:47:50Z
canonical: "docs.senhasegura.io/certificates-flow-how-to-publish-a-certificate"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish a certificate

Publish a signed certificate to a device registered in Segura™. Segura™ verifies the certificate's authenticity and integrity during publishing.

Info

Segura™ supports the following publishing profiles: **Apache**, **Tomcat**, **Nginx**, **IIS**, **Kubernetes**, **Netscaler**, **IBM Websphere**, **F5 BigIP**, **Palo Alto**, and **CURL**.

## Requirements

- The device must already be registered in Segura™.
- A valid certificate.
  - Manually imported certificates must include their respective keys.
- When using the **NetScaler** as the publishing profile, the certificate must have at least a 6-character password.

## Publish a certificate

1. On Segura™, in the navigation bar, hover over the **Products menu** and select **Certificate Manager**.
2. In the side menu, select **Certificates > SSL/TLS**.
3. In the desired certificate, click **Actions > Publish certificate**.
4. In the **General** tab, enter the following information:
  1. In the **Reason *** field, select a reason for publishing the certificate.
  2. In the **Governance Code** field, enter a governance code.
  3. In the **Publishing profile** field, select the publishing profile.
  4. In the **Create a new publishing profile** field, select to create a new publishing profile.
  5. In the **Publication profile name** field, enter a name for the new publishing profile. This field is only available after selecting the **Create a new publishing profile** checkbox.
  6. In the **Publishing plugin**, select the publishing profile. This field is only available after selecting the **Create a new publishing profile** checkbox.
  7. In the **Justification** field, enter a justification for publishing the certificate.
  8. In the **Use a registered credential to access all devices** field, select to use a registered credential to access all devices.
  9. In the **Access credential registered in the system** field, select the registered credential to be used. This field is only available after selecting the **Use a registered credential to access all devices** checkbox.
  10. In the **Credential username** field, enter a username. The system matches it against credentials on the registered devices, so the device must have a credential with the same username.
5. Click **Continue**.
6. Optional: In the publishing profile tab, enter the information according to the profile selected in step 4.. For more information on each profile, see [Publishing profiles](/v4-2/docs/clm-publishing-profiles#publishing-profiles).
7. In the **Servers** tab, click **+ Add** to select the servers where the certificate will be published.
  1. Select the desired servers, and click **Add**.  

:::(Warning) (Attention) Ensure that the credential selected in the **General** tab can connect to the chosen servers. :::
8. Click **Continue**.
9. Optional: In the **Schedule** tab, enter the following information about publication schedule:
  1. In the **Enabled** field, select to schedule to publication.
  2. In the **Date and time of publication** field, schedule the date and time of the publication. This field is only available after selecting **Yes** in the **Enabled** field.
10. Click **Continue**.
11. In the **Review** tab, review all information entered previously, and click **Save**.

The newly published certificate will appear on the [SSL/TLS certificates](/docs/certificate-manager-reference-certificate-certificate-2) report screen.