Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[FEATURE REQ] How to migrate certificates configuration

See original GitHub issue

Please describe the feature.

Our backend require us to define configuration with certificates which are managed in different Key Vaults specific to each environment.

What is the best way to add those certificate configuration to the APIM ?

We can see that once the certificate is added, we can use the backend to configure the service by using following setup…

backends:
  - name: "my-backend"
    properties:
      url: "https://myservice.com"
      credentials:
        certificate: ["xxxxxx"]

Issue Analytics

State:
Created 7 months ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

vtapadiacommented, Feb 14, 2023

We fixed the final issue by having the same name of certificate accross all environments.

The only thing that we had to do outside was certificate registration to the APIM platform.

Another issue we noticed was that when using the same certificate with a different name, the APIM was not allowing us to add it. Its strange that they work with names, but implementation is based on actual certificate. But I guess that is not an issue for you guys… 😃.

Thanks for the help and useful discussion. We are going to use this process more and will report any findings we may have in the future.

1reaction

waelkdouhcommented, Feb 9, 2023

I agree with everything you suggested.