Create a self-signed certificate for recording traffic in Leapwork Go | Leapwork Docs

This article explains how to generate a self-signed certificate bundle that Leapwork Go can use to record HTTPS traffic. The scripts mirror the bundled Leapwork Go Recorder certificate workflow and generate the PEM files required for upload.

This is only required if you choose to use your own self-signed certificate instead of the default certificate provided by Leapwork.

After generating a new certificate and uploading it to the Admin Portal, it must be added to the Trusted Root Certification Authorities store on all user machines. If this step is not completed, recording functionality will not work as expected.

Before you start

Make sure:

Install OpenSSL (if needed)

Windows

https://slproweb.com/products/Win32OpenSSL.html


macOS

If OpenSSL is not already available:

Install Homebrew:


Install OpenSSL:


Verify:


Generate the certificate on macOS

Use this script on macOS to create the certificate and key files that Leapwork Go needs for HTTPS traffic recording.

  1. Save the script below as generate-leapGo-certificate.sh in an empty folder.
   
  1. Replace <Your organization name> and <Leapwork Go Recorder CA> if needed.
  2. Run:

Generate the certificate on Windows

  1. Open PowerShell.
  2. Save the script below as Generate-LeapGo.ps1 in an empty folder.
   
  1. In the script, replace Your organization name with your company name.
  2. Keep Leapwork Go Recorder CA as the certificate name, or replace it with your preferred common name.
  3. Run:

Files generated

The scripts generate these files:

Keep mitm-key.pem, key_pkcs8.pem, and bundle.pem secure.

Upload the certificate to Leapwork Go

  1. Sign in to the Leapwork Admin Portal.
  2. Open the profile section.
  3. Use the certificate upload option.
  4. Upload bundle.pem.

Validate the generated files

To confirm that generation worked:


Troubleshooting common issues

1. Why do I see “openssl is not found”?

This means OpenSSL is not installed or not available in your system PATH.

Solution:


This change applies only to the current session.

2. Why is PowerShell blocking the script?

PowerShell may prevent scripts from running due to execution policy restrictions.

Solution:

Run the following command before executing the script:


Then run the script again.

3. Why is bundle.pem missing?

This usually means one or more OpenSSL commands failed during execution.

Solution: