Guide
TrainingSupportCommunity

Signature Header Authentication

Suggest Edits

This behavior provides header-based verification of outgoing origin requests.

How it works

Edge servers encrypt request data in a pre-defined header, which the origin uses to verify that the edge server processed the request. You can use this behavior to configure the request data, header names, encryption algorithm, and shared secret to use for verification.

Features and options

FieldWhat it doesSub-options
StatusEnables or disables the behavior.
Clear Data Header NameSpecifies the name of the header containing the request data that needs to be encrypted.
Encrypted Data Header NameSpecifies the name of the header containing encrypted request data.
Encryption Algorithm VersionSpecifies the version of the encryption algorithm that you want to use to encrypt the data.
  • MD5(key, data, sign-string)
  • MD5(key,MD5(key, data, sign-string))
  • MD5-HMAC(key, data, url)
  • SHA1-HMAC(key, data, sign-string)
  • SHA256-HMAC(key, data, sign-string)
Signed String TypeSpecifies whether the encrypted string is based on the forwarded URL or a custom set of data. By default, the encrypted string is based on the forwarded URL.
  • Default (Forwarded URL)
  • Custom
DataWith Signed String Type set to Custom, specifies the set of data to be encrypted as a combination of concatenated strings.
  • Incoming Request Method
  • Incoming Request (http or https)
  • Incoming Request Hostname
  • Incoming Request Domain
  • Incoming Request URL
  • Incoming Request Path
  • Incoming Request Query String
  • Incoming Request Filename
  • Incoming Request Filename Extension
  • Incoming Request Client IP
Secret KeySpecifies the shared secret key.
NonceSpecifies the cryptographic nonce string.

Note: The value of the nonce cannot be the same as the value of the shared secret key.

Updated about 3 years ago