These failed login attempts correspond with the following NSX Manager log entries that are similar to the below:
/var/log/proxy/reverse-proxy.log
2026-06-10T11:08:37.890Z INFO Processing request <Request ID> OAuth2AuthenticationProvider 3180 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="http"] Bypassing local login attempt.
2026-06-10T11:08:37.890Z INFO Processing request <Request ID> CustomOidcAuthorizationCodeAuthenticationProvider 3180 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="http"] Bypassing local login attempt.Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
VMware NSX
This behaviour is by design. In NSX versions prior to NSX 4.2.4 or 9.0.0, vIDM users could login directly to the NSX UI. The correct NSX UI authorization workflow is to enter credentials in vIDM which then redirects to the NSX UI.
A fix to prevent local NSX login requests from bypasssing vIDM was included in NSX 4.2.4 and 9.0.0.
This is a condition that may occur in a VMware NSX environment.
The correct NSX UI authorization workflow to follows is below: