2. Set a secure vault password on server-side and client-side appliances. See Managing user permissions.

3. On the server-side SteelHead, configure a proxy certificate and private key for the SSL back-end server. See About server certificates.

4. Create an in-path rule on the client-side SteelHead. For in-path configurations, set the preoptimization policy to SSL. If you want to enable the HTTP latency optimization module for connections to the specified server, create an additional in-path rule and set the latency optimization policy to HTTP. For out-of-path configurations, create a fixed-target in-path rule that identifies the connections which to apply SSL acceleration. Set VLAN tagging to All, preoptimization policy to SSL, data reduction to Normal, latency optimization to HTTP (or None for applications that use SSL but are not HTTP-based), and neural framing to Always. See About Peering, Autodiscovery, In-Path Rules, and Service Ports.

5. Configure the server-side and client-side appliances as mutually trusted peers. See About peer trust tables.

6. If your organization uses internal CAs to sign their SSL server certificates, you must import each of the certificates (in the chain) on to the server-side appliance. You must perform this step if you use internal CAs because the appliance’s default list of well-known CAs doesn’t include your internal CA certificate. See About server certificates.

7. Restart the optimization service on all relevant appliances. See Restarting the optimization service.