TLS_GATEWAY_CP defaults to Y when it should default to N per docu
search cancel

TLS_GATEWAY_CP defaults to Y when it should default to N per docu

book

Article ID: 245631

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

In WP logs, TLS_GATEWAY_CP is set to Y even if it has not been set in UC_SYSTEM_SETTINGS; so it is defaulting to Y:

20220606/032517.441 - 20220602/075746.649 - U00011847 'TLS_GATEWAY_CP' set to 'Y'.

According to https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/21.0.3/Automic%20Automation%20Guides/Content/AWA/Variables/UC_SYSTEM_SETTINGS/UC_SYSTEM_TLS_GATEWAY_CP.htm it should be set to N by default:

Systemwide variable that enables you to decide if the TLS Gateway can be used as a communication process (CP) for non-TLS/SSL Agents.

  • Allowed values: YES and NO

  • Default value: NO

  • Restart required: No

 

Environment

Release : 21.0.2

Component : AUTOMATION ENGINE

Resolution

This will be fixed will 21.0.4

Workaround: explicitly set TLS_GATEWAY=N in UC_SYSTEM_SETTINGS

Powered by Wolken Software