Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

Be able to Sync Certificates using Tyk Sync #40

Open
chris-fewtrell opened this issue Jul 14, 2020 · 2 comments
Open

Be able to Sync Certificates using Tyk Sync #40

chris-fewtrell opened this issue Jul 14, 2020 · 2 comments

Comments

@chris-fewtrell
Copy link

Be able to dump and publish certificates.

Scenario:
Working in multi customer scenario, where each customer runs own sandbox environment of Tyk cluster with Dashboard. Dump APIs policies and supporting certificates from each customer sandbox to import merged set into a staging platform to test the combined estate. Each customer is running in its own org, and all orgs are expected to exist in the staging platform (copied via Tyk-Sync as required). It would be desirable to use one tool to integrate with CI/CD workflow managers to handle transfer of APIs from one environment to another and run tests, rather than have to sync certificates via another automation.

Tyk Ticket Ref: 10745

@tapiosa
Copy link

tapiosa commented Mar 31, 2022

This functionality would be great for our use-case as well. We have an active datacenter serving the traffic, but also a passive one that will be used when active one is lost. Being able to sync the client certificates from active to passive would be needed.

@buger
Copy link
Member

buger commented Mar 31, 2022

Hi!

Some good news here.
For 4.1 release we are making it a built-in capability in Tyk Gateway.
It will automatically syncronise all active API keys, Certificates, oAuth Clients and etc, so another datacenter will be fully working even master data center goes down. The only pitfall here is that it will work only with our MDCB (multi-data center offering).

As quick and dirty solution will be litelary dumping all "cert-*" keys from one redis, and transfering them to another redis.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants