Token Authentication for Cached Private Content and APIs

What this post added

Introduced Token Authentication as a feature to control access to cached private content and APIs. This feature leverages HMAC tokens generated from a shared secret, resource path, and timestamp. Tokens can be passed as URL parameters or HTTP headers. The validation occurs at the edge, preventing invalid requests from reaching the origin and enabling caching of protected content. The post provides implementation examples in PHP for generating tokens and mentions configuration options within the WAF Custom User Rule Set Package.