Last Modified: Oct 19, 2025
Affected Product(s):
APM-Clients APM
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, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 15.1.10.7, 15.1.10.8, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1
Fixed In:
7.2.4.7
Opened: Aug 25, 2020 Severity: 3-Major
-- In case of errors against OAuth Token Endpoint, the OAuth done page is displayed in the default web browser. -- Edge Client UI displays the message, 'Waiting to connect to server' -- Multiple new tabs with OAuth done opens in the existing default web browser.
-- Edge Client cannot complete the OAuth logon and hence the Access policy, so the end user client cannot connect to the VPN. -- BIG-IP Administrators may have issues troubleshooting this failure, as the exact reason for the failure is not indicated in the UI or the logs.
-- OAuth settings configured in the connectivity profile for a virtual server. -- OAuth logon encounters an issue with the token endpoint while trying to get the Access Token in exchange for the Authorization code. One example of this is the client_secret field needed for Google Authenticator, Microsoft Azure, and others, which may not be provided by Edge Client.
None.
Once the detection of the error code occurs for the invalid oAuth token, try to re-authenticate for couple of times before disconnecting the VPN.