As we reach the end of September 2024, ThreadFix version 3.x on-premises has officially reached its End-of-Life. Therefore, there is no longer support or updates for this version of the product. We have fully transitioned our product and development teams to focus ThreadFix SaaS and migrating all customers over from the on-premises versions. Our Customer Success and Support teams are here to help you in migrating to ThreadFix SaaS and maximizing the value you see from this improved offering from Coalfire. This is the next phase of ThreadFix and our team is looking forward to continuing to support you on this journey.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

You will learn

📙

How to update a TLS certificate.

Prerequisites

Audience: IT Professional
Difficulty: Intermediate
Time needed: Approximately 10 minutes
Tools required: If any

Updating a Certificate

Follow this section to change an existing TLS certificate, if desired.

*If the previous guides were followed, the TLS certificate will be named tf-tls. If a certificate was installed with a different name, replace tf-tls with the name being used.

  1. Acquire a TLS certificate from a trusted provider.

  2. Convert the certificate into base64 encoded PEM format. Follow vendor instructions for converting the current certificate to PEM, if it is not in the correct format.

  3. Delete the existing TLS secret:

    kubectl delete secret tf-tls

     

  4. Run the following (replacing and with their respective paths):

    kubectl create secret tls tf-tls --key <tls-key> --cert <tls-cert>

     

  5. Set the Kong deployment name:

    TF_KONG_DEPLOY=$(kubectl get deploy -l app.kubernetes.io/name=kong -o jsonpath='{.items[].metadata.name}')

     

  6. Restart kong:

    kubectl rollout restart deploy $TF_KONG_DEPLOY
  • No labels