Configuring URL Encryption

To enable encryption of the dynamic fields in the redirected URL, use the following sample configuration:

configure 
   active-charging service service_name 
      charging-action charging_action_name 
         flow action redirect-url redirect_url [ encryption { blowfish128 | aes256 } [ encrypted ] key key ] 
      end 

NOTES:

  • flow action redirect-url redirect_url —Specify the redirect URL. It can include up to 16 dynamic fields. redirect_url must be an alphanumeric string of 1 through 511 characters.

  • encryption { blowfish128 | aes256 } [ encrypted ] key key —Specify to enable encryption for dynamic fields of the redirect URL.

    • blowfish128 —Specify to use Blowfish encryption with 128-bit key for encrypting the dynamic fields.

    • aes256 —Specify to use AES-CBC encryption with 256-bit key for encrypting the dynamic fields.

    • encrypted —Specify to encrypt the key.

    • key key —Specify the key to use for encryption of dynamic fields. key must be an alphanumeric string of 1 through 523 characters.

  • If encoding is enabled in the URL to be redirected, the encrypted URL supports up to 2300 characters. If the length exceeds, then the URL will be truncated at 2300 characters.