Smarts SAM: Setting up secure communication between SAM and W4N: incoming/outgoing set to 3,1 doesn't work

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Setting up secure communication between SAM and W4N: incoming/outing set to 3,1 doesn't work

Environment

VMware Smart Assurance - SMARTS

Cause

This has been tested by Engineering in the lab and no matter what you set the values to for the Watch4Net to SAM Server communication, it will fall back to 0, as the Watch4Net to SAM Server encrypted communicated is not possible.

This is also stated on page 18 of the Smarts Security Guide 9.4 that only cleartext is possible. 

Note: TLS is not supported between Watch4net and SAM.

Resolution

It is working as designed.