--- title: Update a Certificate for the Swimlane Web Interface slug: install-10x/update-a-certificate-for-the-swimlane-web-interface docTags: createdAt: 2025-12-15T07:17:59.686Z --- The steps below will update the current SSL certificate used with the Swimlane web application. The private key cannot be password protected. The certificate must be base64-encoded ASCII X.509, as noted in this excerpt from the [DigiCert® SSL/TLS Best Practice Workshop Student Guide](https://www.digicert.com/content/dam/digicert/pdfs/ssl-tls-best-practice-workshop-student-guide-en.pdf): "... Most CAs (Certificate Authority) provide certificates in PEM format in Base64 ASCII encoded files. *The certificate file types can be .pem, .crt, .cer, or .key. The .pem file can include the server* *certificate, the intermediate certificate and the private key in a single file. The server certificate and* *intermediate certificate can also be in a separate .crt or .cer file. The private key can be in a .key file.* *PEM files use ASCII encoding, so you can open them in any text editor such as notepad, MS word etc.* *Each certificate in the PEM file is contained between the ---- BEGIN CERTIFICATE---- and ----END* *CERTIFICATE---- statements. The private key is contained between the ---- BEGIN RSA PRIVATE KEY---* *-- and -----END RSA PRIVATE KEY----- statements. The CSR is contained between the -----BEGIN* *CERTIFICATE REQUEST----- and -----END CERTIFICATE REQUEST----- statements.* ..." 1. Take a backup of the existing certs: :::BlockQuote{indent="1"} \# Replace \ with the name of the web pod kubectl cp \:/run/secrets/swimlane.crt swimlane.crt kubectl cp \:/run/secrets/swimlane.key swimlane.key ::: 2. Access the SPI Admin Console https\://{URL}:8800) 3. Visit the Config page 4. Under “Upload a certificate for Swimlane Web”, upload new certificates or update existing certificates 5. Scroll to the bottom of the page to “Save config” 6. Continue and re-deploy to the same Swimlane version