Unable to log in to the vSphere UI after registering a new vCenter Server to vRealize Operations Manager (formerly known as VMware vCenter Operations Manager)
search cancel

Unable to log in to the vSphere UI after registering a new vCenter Server to vRealize Operations Manager (formerly known as VMware vCenter Operations Manager)

book

Article ID: 340578

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:

After registering a new vCenter Server to vRealize Operations Manager (formerly known as VMware vCenter Operations Manager), you experience these symptoms:

  • You are unable to log in to the vSphere UI
  • Attempting to login to the vSphere UI via a Web browser as an AD/vCenter Server user fails
  • You see one of these error:
Incorrect User name/Password.

Or

Invalid username/password
  • In the web_std.log file, you see errors similar to:
2013-02-05 17:47:13,026 ERROR [TP-Processor1] com.integrien.alive.vm.ConfigurationManagerImpl.execute - Invalid user credentials
  • In the vpxd.log file of the recently added vCenter Server, you see entries similar to:

2013-02-05T23:47:17.597Z [7F82D581C700 info '[SSO]' opID=7cb9f6b4] [UserDirectorySso] Authenticate(someuser, "not shown")
2013-02-05T23:47:17.627Z [7F82D581C700 error '[SSO]' opID=7cb9f6b4] [UserDirectorySso] AcquireToken InvalidCredentialsException: Authentication failed: Authentication failed
2013-02-05T23:47:17.627Z [7F82D581C700 error 'authvpxdUser' opID=7cb9f6b4] Failed to authenticate user <someuser>
2013-02-05T23:47:21.637Z [7F82D581C700 info 'commonvpxLro' opID=7cb9f6b4] [VpxLRO] -- FINISH task-internal-4414 -- -- vim.SessionManager.login --
2013-02-05T23:47:21.637Z [7F82D581C700 info 'Default' opID=7cb9f6b4] [VpxLRO] -- ERROR task-internal-4414 -- -- vim.SessionManager.login: vim.fault.InvalidLogin:
--> Result:
--> (vim.fault.InvalidLogin) {
--> dynamicType = <unset>,
--> faultCause = (vmodl.MethodFault) null,
--> msg = "",
--> }
--> Args:
-->



Cause

This issue occurs when there is a vCenter Server registered to vRealize Operations Manager in which the AD/vCenter Server credentials entered cannot be authenticated. This usually occurs when one vCenter Server is not a part of the same AD domain as the rest.

Resolution

To resolve this issue, ensure that all registered vCenter Servers are joined to the same AD domain or that a trust exists between the domains, such that the user account used to log in to vRealize Operations Manager has the appropriate access privileges on all registered vCenter Servers.
If modifying the AD domain membership or AD trust configuration is not an option, try this workaround:
  1. Log in to the UI VM as the root user.
  2. Open the /usr/lib/vmware-vcops/tomcat/webapps/vcops-vsphere/WEB-INF/aliveconfig.properties file using a text editor.
  3. Add this entry at the end of the file.
ignoreInvalidLogin=true
  1. Save and close the file.
  2. Restart the vRealize Operations Web interface using this command:

    service vcopsweb restart

Note: This issue is usually seen to occur when a vCenter Server Appliance that is not joined to any AD domain is added to an existing vRealize Operations Manager installation.


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box