Skip to main content

 

IdP Misconfiguration Causing vIDM Login Failures with OAuth2 "The error message displayed is: https://load-balancer/hc/error."


Issue/Introduction

This article addresses intermittent login failures encountered by users in a vIDM  environment utilizing OAuth2 authentication with a load balancer. 

Environment

VMware Identity Manager 3.3.7 

Cause

The intermittent login failures likely stem from a mismatch between the Vidm Connector hostname configured in the Identity Provider (IdP) and the actual hostname used by the load balancer.

Resolution

Scenario 1: Single Connector, VIP Address:

Update IdP Configuration:

Ensure the vIDM Connector hostname (e.g., myconnector.mycompany.com) is configured in the IdP for OAuth2 client settings, not the load balancer hostname (e.g., mylb.mycompany.com).

The IdP was configured with the VIP address of the load balancer instead of the individual vIDM Connector hostname.
This can lead to login failures if the user is directed to a vIDM Connector not configured in the IdP.

Scenario 2: Multiple Connectors, Single Connector Added:

Add All Connectors to IdP (if applicable):
If your environment utilizes multiple vIDM Connectors behind the load balancer, verify that all connectors are registered in the IdP for OAuth2 client settings. This ensures users can be directed to any available connector for authentication.

How to add the connector to IDP: ADD connectors

Additional Information

The provided information suggests that initially only one connector was added to the IdP with the VIP address. This configuration can cause login failures for users directed to non-configured connectors.

Labels:

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 ðŸ”¹ Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
Post a Comment
Read more