[VMC on AWS] Context Profile with wildcard FQDN does not work via FQDN Filtering

Products

• VMware Cloud on AWS

Issue/Introduction

To clarify and provide a workaround for the customer.

Symptoms:
SDDC is on version 1.22v2 and below.
When only the wild card of the FQDN (*.fqdn.com) is added in the Context Profile attributes, the base domain (https://www.fqdn.com) is unable to be accessed. However, the subdomains within the FQDN (https://sub1.fqdn.com, https://sub2.fqdn.com) are able to be accessed. 

Cause

This is currently a known bug in SDDCs version 1.22v2 and below.

Resolution

This has been patched and resolved in SDDC version 1.22v3 and above.

Workaround:

• Use the wildcard (*.fqdn.com) if user is accessing subdomains within the FQDN (for e.g. https://sub1.fqdn.com, https://sub2.fqdn.com). 
• The base domain (fqdn.com) will also need to be added to the FQDN filters if the user would like to access the base domain (for e.g. https://www.fqdn.com)

Additional Information

https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-63262728-CA72-47D2-8E4F-16617B63A9A4.html#GUID-63262728-CA72-47D2-8E4F-16617B63A9A4

Impact/Risks:
Customers will be unable to browse webservers that are listed in Context Profile FQDN.