As our team continues to work with utilizing Layer 7 API Gateway as a container, we are finding ourselves struggling to develop a solution that is fully managed ‘as-code’. We are revisiting an issue which was previously discussed where the API Gateway requires a restart in order to pick up the correct keystore. From our previous discussions, we implemented a solution that uses key aliases and sets the policies accordingly to use them. What appears to be happening now is…
Release : 10.1
Need dynamic updates doing one call/update to work around they needed to touch the policy or restart (simulates load/active from PM)
New Feature
Using the new feature added in Gateway 10.1 CR2
Use dynamic private key -> Use Dynamic Private Key -> Key Alias (variable)
Allows for the use of a context variable