Zum Hauptinhalt gehen
 

Wie können wir helfen?

Suche

Beiträge in diesem Abschnitt

[en] Secure End-User Communication with Acrolinx

  • Aktualisiert

[en] If you use Standard Stack, it’s a good idea to secure end-user communication with Acrolinx. When you configure the Transport Layer Security (TLS) certificate in the ingress, your Acrolinx users can reach the platform UI via the secured transport layer protocol HTTPS.

[en] Generate TLS Key and Certificate

[en] Before you get started, you’ll need a TLS key and certificate.

Tipp

[en] Check out the Kubernetes documentation to make sure that your certificate is in the right format.

Tipp

Please note that self-signed certificates may not be used. If your server is configured for an SSL connection, the Sidebar will only work if you install an SSL certificate from an independent certificate authority.

[en] Serve Dashboard Through HTTPS

[en] To serve the Dashboard through HTTPS via certificate and ingress, do the following:

  1. [en] Upload the certificate into your cluster.

    kubectl -n acrolinx create secret tls acrolinx-tls-cert --cert=path/to/tls.cert --key=path/to/tls.key

  2. [en] Now, set the platform.spec.ingress.tlsSecretName variable to tell the Acrolinx Platform to use the certificate you just added. You’ll need to configure it in the acrolinx.yaml file. See Configure the Acrolinx Operator for more information.

    spec:
  set:
    ### [...]
    platform.spec.ingress.tlsSecretName: "acrolinx-tls-cert"

    Anmerkung

    [en] After you edit the file, don't forget to apply your changes with kubectl apply -f acrolinx.yaml.