Create HTTP Header Insertion Entries using Predefined Types

1. If there are no upstream devices already decrypting HTTPS traffic, configure decryption using Configure SSL Forward Proxy.

   If you're configuring SSL decryption for Dropbox, then you must also configure your Dropbox clients to allow SSL traffic. These procedures are specific and private to Dropbox. To obtain these procedures, contact your Dropbox account representative.

   1. Add a custom URL category for the SaaS application you're managing (ObjectsCustom ObjectsURL Category).
   2. Specify a Name for the category.
   3. Add the domains specific to the SaaS application you're managing or for which you want to insert the username and domain in the headers. See Domains used by the Predefined SaaS Application Types for a list of the domains that you use for each of the predefined SaaS applications. See Insert Username in HTTP Headers for more information on configuring the firewall to include the username and domain in the HTTP headers.

      Each domain name can be up to 254 characters and you can identify a maximum of 50 domains for each entry. The domain list supports wildcards (for example, *.example.com). As a best practice, do not nest wildcards (for example, *.*.*) and do not overlap domains within the same URL profile.
   4. For SaaS application management, create a decryption policy rule and, as you follow this procedure, configure the following:

      • In the Service/URL Category tab, Add the URL Category that you created in the previous step.
      • In the Options tab, make sure the Action is set to Decrypt and that the Type is set to SSL Forward Proxy.
2. Edit or create a URL Filtering profile.
3. Select HTTP Header Insertion in the URL Filtering Profile dialog.
4. Add an entry.

   1. Specify a Name (up to 100 characters) for this entry.
   2. Select a predefined Type.

      This populates the Domains and Headers lists.
   3. For each Header, enter a Value.

      Each header value can have up to 16 thousand characters.
   4. (Optional) Select Log to enable logging of insertion activity for the headers.

      Allowed traffic is not logged, so header insertions are not logged for allowed traffic.
   5. Click OK to save your changes.
5. Add or edit a Security policy rule (PoliciesSecurity) to include the HTTP header insertion URL Filtering profile.

   • For SaaS application management, allow users to access the SaaS application for which you're configuring this header insertion rule.
   • To include the username and domain in the HTTP headers, apply the URL Filtering profile to the Security policy rule for HTTP or HTTPS traffic.

   1. Choose the URL Filtering profile (ActionsURL Filtering) that you edited or created in step 2.
   2. Click OK to save and then Commit your changes.
6. Verify that the firewall correctly inserts the header.

   • For SaaS application management, from an endpoint, confirm that access to the SaaS application is working in the way you expect.
     1. Try to access an account or content that you expect to be able to access. If you cannot access the SaaS account or content, then the configuration is not working.
     2. Try to access an account or content that you expect will be blocked. If you can access the SaaS account or content, then the configuration is not working.
     3. If both of the previous steps work as expected, examine the URL Filtering logs for recorded HTTP header insertion activity (if you configured logging in step 4.4).