User access blocked because application is not configured as a gateway service

Products

• CASB Securlet SAAS

Issue/Introduction

Deactivating a gatelet caused a SaaS outage for the gatelet that eventually started working after the error went away.

Resolution

Deactivating a gatelet requires 2 steps.  Selecting deactivate on the gatelet and a finalize button to be selected after hitting deactivate.

The deactivate gatelet sends data to WSS to clean up the gatelet detail. The finalize is then selected at which time the gatelet detail is removed from CloudSOC.

After hitting deactivate on a gatelet do not hit Finalize Deactivation of App until WSS has been cleaned up (usually takes 1-2 minutes). There is not a problem to give it a day or longer.  Once WSS does not know about the gatelet it is essentially inactive.

Check Threatpulse | Policy | CASB Gatelets for verification the gate is removed

 

Additional Information

An issue was fixed for 3.158 to address the first stage of deactivation to ensure WSS is updated.