exp_param_name
Defines the name of the secure token parameter for Akamai CDN.
Description
The exp_param_name directive is used to specify the name of the secure token parameter that will be embedded in requests for content served through Akamai's CDN. This directive allows you to customize how the secure token is named in the URL or as part of the query string, enhancing control over how tokens are generated and utilized with different APIs or client needs. For instance, if you wish to use a particular naming convention (like exp instead of the default), this directive allows that flexibility.
When this directive is set, the secure token is constructed using the specified parameter name alongside other vital components, such as the access control list (ACL), start and end times, and an HMAC hash for the overall security of the token. This ensures that the token is both uniquely identifiable and secure, following the standards required by systems like Akamai that rely on tokenized access to media content.
In practice, this directive is a critical part of the token generation process and must be paired with other related configurations to ensure that headers, caching, and expiration timings are correctly handled. Without properly setting this directive, token-related requests may fail due to misnamed parameters, causing the content delivery to not authenticate properly, leading to unauthorized access or denial of service.
Config Example
secure_token_akamai {
param_name exp;
key some_secure_key;
acl allowed_access_granted;
start 1630454400;
end 1630458000;
}Ensure the parameter name does not conflict with existing query parameters used by the application.
Remember to update client-side code if changing the param_name to recognize the new token name.
Consider the implications of caching when changing the parameter name, as cached content may rely on original token configurations.