A config key defines a container's entire configuration. It is referenced whenever a container is deployed, starts or scales up.
It may become necessary to replace the config key in use with a new one. Reasons for replacing a key include:
It is suspected that the config key in use has been leaked.
Security compliance requirements mandate rotating config keys.
If a config key in use is regenerated, the container and applications associated with it will stop working. They must be redeployed with a new key. Barracuda WAF-as-a-Service allows you to easily generate and rotate keys.
Generating a New Config Token
In the WAF-as-a-Service web interface, click Resources in the left-hand panel.
Navigate to WAF Containers > Container Management.
On the Container Management page:
Find your container in the table and click the three-dot menu under ACTION.
Select Manage Config Keys.
The Manage Config Keys window will open, displaying the two config keys.
Click the Regenerate link to replace either one with a newly generated key.
Rotating a Config Key
To switch a container to a different config key, do the following:
In the WAF-as-a-Service web interface, click Resources in the left-hand panel.
Navigate to WAF Containers > Container Management.
On the Container Management page:
Find your container in the table and click the three-dot menu under ACTION.
Select Manage Config Keys.
Copy the config key that you want to use.
Manually edit the container deployment file you used to deploy the container. Replace the old config key with the new one.
If you no longer have the container deployment file, you can Create a New Container Deployment File. As you go through the wizard to help you create a new file, select the new config key on the Container Deployment Advanced Options screen, and then Redeploy the Container.