Following the update to Web Security Service (WSS) in November 2017, WSS requires a specific set of criteria to integrate it with ProxySG appliances. Previous WSS/ProxySG integrations, where this configuration required that ProxySG administrators were required to enter the WSS login credentials on the ProxySG are invalidated by this change.
When integrating WSS and ProxySG in the current system, the only permitted username is sg-register. The password for the service is generated as a token in the WSS portal. WSS uses this token to identify the appropriate Web Security Service account.
This article details the steps to configure WSS and ProxySG integration.
This configuration takes place in two parts - Configure WSS to expect a connection from your ProxySG appliance(s) using a unique token, then configure your ProxySG appliance(s) to use that token.
Web Security Service Portal
For a location named SatelliteOffice1, using the token from the WSS portion of this procedure above:
(cloud-service)# register SatelliteOffice1 sg-register 190072n6-cb0e-4a7a-b1b3-a6767e4e27b8