Bug ID 937213: Virtual Server is not created when a new HTTPS virtual server is defined with a new security policy

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5

Opened: Aug 17, 2020
Severity: 3-Major

Symptoms

Virtual Server is not created when a new HTTPS virtual server is defined with a new security policy using GUI page.

Impact

The virtual server is not created when you create the policy, and HTTPS security will not be applied to this newly created security policy.

Conditions

- In GUI open "create new policy" page - Assign a policy name in "Policy Name" - Assign "Fundamental" for "Policy Template" - Choose "Configure new virtual server" in "Virtual Server" - Select "HTTPS" for "What type of protocol does your application use?" - Choose an IP address and port 443 for "HTTPS Virtual Server Destination" - Choose an IP address and port 443 for "HTTPS Pool Member" - "clientssl" for "SSL Profile (Client)" - "serverssl" for "SSL Profile (Server)" - click on "Save" button to create new policy

Workaround

Go to the Local Traffic section and create a HTTPS Virtual Server manually. After that, assign the security policy to the Virtual Server.

Fix Information

None

Behavior Change