Symptoms

In previous releases, some invalid combinations of Profile Type and User Identification Methods were allowed via either the UI or tmsh.

Impact

It is possible to create and use non-allowed profile type-user identification methods. Then, during upgrades, the following Profile types will have their user identification method automatically set to the corresponding values in the following table because other methods are not supported. Profile Type | User Identification Method --------------------------------------------- OAuth-Resource-Server| OAuth Token SSL-VPN | HTTP System Authentication| HTTP

Conditions

Use of invalid Profile types and User Identification methods is possible and they wont work.

Workaround

You can reconfigure the user identification method to list of allowed ones: Profile Type | User Identification Method --------------------------------------------- All | HTTP LTM-APM | {HTTP | IP Address} OAuth-Resource-Server| OAuth Token SSL-VPN | HTTP SWG-Transparent | IP Address SWG-Explicit | {IP Address | Credentials} System Authentication| HTTP

Fix Information

During upgrades, the following Profile types will have their user identification method automatically set to the corresponding values in the following tables because other methods are not supported. Warning message will be logged for each upgrade set required. In earlier releases, users were not prevented from selecting such user id methods. Profile Type | User Identification Method --------------------------------------------- OAuth-Resource-Server| OAuth Token SSL-VPN | HTTP System Authentication| HTTP

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips