central_authorization
Version: v2025-01-13 | Includes use: Yes |
---|
Behavior name: Centralized Authorization
Forward client requests to the origin server for authorization, along with optional Set-Cookie
headers, useful when you need to maintain tight access control. The edge server forwards an If-Modified-Since
header, to which the origin needs to respond with a 304
(Not-Modified) HTTP status when authorization succeeds. If so, the edge server responds to the client with the cached object, since it does not need to be re-acquired from the origin.
Default behavior
These samples reflect the behavior's default settings. You can use these as is in your configurations or make adjustments based on the behavior's available options.
data "akamai_property_rules_builder" "central_authorization" {
rules_v2025_02_18 {
name = "Centralized Authorization"
comments = "Forwards client requests to the origin server for authorization."
behavior {
central_authorization {
enabled = true
}
}
}
}
"behaviors": [
{
"name": "centralAuthorization",
"options": {
"enabled": true
}
}
]
Options
Option | Description |
---|---|
enabled |
Enables the centralized authorization behavior.
|
Updated 1 day ago