Configure IaaS Web Application Firewall Appliance (PUT)
Updated: July 12, 2016
Configure a WAF on an existing deployment.
Request
Method |
Request Uri |
---|---|
PUT |
https://<endpoint>/subscriptions/{subscriptionId}/resourceGroups/{rg}/providers/microsoft.Security/webApplicationFirewalls/{name}?api-version={api-version} |
Request Uri Parameters
Parameter |
Description |
---|---|
subscriptionId |
The subscription id |
rg |
The name of the resource group the IaaS WAF was created at |
name |
Name for the WAF. The name matches the CSM deployment name that the IaaS WAF was created in (on client side). |
Api-version |
The version of the Security RP protocol used for this request |
Request Headers
Common request headers only.
Request body
{
“Properties” :
{
"taskId": "061bae8a-ed30-4c58-8995-9899d550de9e",
"templateId":"Rome.BarracudaWebApplicationFirewallWAF78.0.2.0",
"customData":
{
“licenseType” : “”,
“licenseKey” : “”,
“domain” : “”,
“aplicationType” : “”,
“securityLevel” : “”
}
}
}
Request Body Parameters
Parameter |
Description |
---|---|
taskId |
Optional, the Rome Task ID that detected the missing WAF |
templateId |
The ID of the template that was used to create the deployment. Must be supported by Rome |
customData |
A set of parameters that will be used to configure the WAF |
Response
Status code
If successful, the operation returns HTTP status code of 202 (ACCEPTED).
Response body
{
“Properties” :
{
"templateId":"Rome.BarracudaWebApplicationFirewallWAF78.0.2.0",
"customData":
{
“licenseType” : “”,
“domain” : “”,
“aplicationType” : “”,
“securityLevel” : “”
}
}
}
See Also
Web Application Firewalls
Security Resource Provider REST API Reference