Global rules
Admin
Update global rule configuration
Changed onUpdates the configuration for a globally configured rule.
This operation can fail for the following reasons:
- Invalid rule name/type (HTTP error 400)
- No rule with name/type rule exists (HTTP error 404)
- A server error occurred (HTTP error 500)
put/admin/rules/{rule}
Request
- The document declares no server URL.
- Authnone declared
Request body
Example request
{
"type": "VALIDITY",
"config": "FULL"
}Response
The global rule's configuration was successfully updated.
Example response
{
"type": "VALIDITY",
"config": "FULL"
}Changes
- warning
added the new
INTEGRITYenum value to theresponse property for the response status - info
added the new
INTEGRITYenum value to the request property
- warning