Deprecation warning: 'client.effective_address'; client.effective_address() is deprecated. Use client.effective_address.connection() or client.effective_address.request()

Products

• Cloud Secure Web Gateway - Cloud SWG

Issue/Introduction

UPE customers using the action client.effective_address() to identify trans-proxy traffic are receiving the following warning (or similar) when pushing the UPE policy to their Cloud SWG tenant: 

14 warnings and 0 errors
...
Deprecation warning: 'client.effective_address'; client.effective_address() is deprecated. Use client.effective_address.connection() or client.effective_address.request() tenant:73710: client.effective_address("$(request.header.Client-IP)","$(request.header.X-Forwarded-For)") 
...

However when using the new actions (client.effective_address.connection() or client.effective_address.request()) pushing the policy returns an error, why and what are the implications of this warning / error?

0 warnings and 4 errors
1 appliance rules cannot be carried over - review analysis report.
Raw CPL requires '#if enforcement=appliance' bracketing for appliance specific policy.

vpm-cpl:6: client.effective_address.connect(("$(request.header.Client-IP)","$(request.header.X-Forwarded-For)")

Environment

Cloud SWG customer using Management Center / UPE to control their policy.

Cause

The deprecation warning comes from the policy ingestion system on the Cloud SWG side.

The error is also coming from the policy ingestion system, which is rejecting the new actions as they are not yet allowed on that system.

Resolution

Currently the legacy action is still available on the Cloud SWG proxies and the warning can be ignored for now.

Engineering is aware of the situtation and the policy ingestion system will be updated in due course to allow the new actions and avoid any service continuity issue for UPE customers using this action.