Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Connector page is blank when connectors are missing an oAuth2ClientId in the database Connector table. (71070)

Last Updated: 10/8/2021Categories: TroubleshootingTotal Views: 20734Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

A node is re-joined to the cluster after it had previously been removed following KB 2149866.

Within Administration, Directories Management or Connectors the re-joined node does not have a connector listed.

Within /var/log/vmware/horizon/horizon.log the below errors are observed when authentication requests hit the re-joined node connector.

Note: The 4 digit connector ID will differ in each enviroment

2019-01-26 13:58:19,525 INFO (Timer-16) [[email-masked];;] com.vmware.horizon.client.rest.IApi - Failed to getOAuth2AccessToken: https://vra.domain.com/SAAS/t/VSPHERE.LOCAL/API/1.0/oauth2/token : 401

2019-01-26 13:58:19,525 WARN (Timer-16) [[email-masked];;] com.vmware.horizon.connector.admin.service.FetchOrgConfigForSAMLAttributeService - Failed to fetch org config for sending password. Continuing to use existing setting.
com.vmware.horizon.connector.exception.HorizonException: Could not get the Suite Token from Service.
at com.vmware.horizon.connector.admin.service.impl.TokenGenerationServiceImpl.getSuiteToken(TokenGenerationServiceImpl.java:46)
at com.vmware.horizon.connector.admin.service.FetchOrgConfigForSAMLAttributeService.getSendPasswordOrgConfig(FetchOrgConfigForSAMLAttributeService.java:99)
at com.vmware.horizon.connector.admin.service.FetchOrgConfigForSAMLAttributeService.syncIfAppropriate(FetchOrgConfigForSAMLAttributeService.java:86)
at com.vmware.horizon.connector.admin.service.FetchOrgConfigForSAMLAttributeService.access$100(FetchOrgConfigForSAMLAttributeService.java:35)
at com.vmware.horizon.connector.admin.service.FetchOrgConfigForSAMLAttributeService$1.run(FetchOrgConfigForSAMLAttributeService.java:61)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: com.vmware.horizon.client.rest.Exception.ApiException: {
"error": "invalid_client",
"error_description": "Client is not found."
}
at com.vmware.horizon.client.rest.Exception.ApiException.buildApiException(ApiException.java:69)
at com.vmware.horizon.client.rest.Api.getOAuth2AccessTokenByClientCredentials(Api.java:235)
at com.vmware.horizon.client.rest.Api.getOAuth2AccessToken(Api.java:113)
at com.vmware.horizon.client.rest.Api.signIn(Api.java:92)
at com.vmware.horizon.client.rest.Api.signIn(Api.java:87)
at com.vmware.horizon.connector.admin.RestHorizonServiceImpl.signIn(RestHorizonServiceImpl.java:136)
at com.vmware.horizon.connector.admin.service.impl.TokenGenerationServiceImpl.getSuiteToken(TokenGenerationServiceImpl.java:40)
... 6 more
Caused by: com.vmware.horizon.client.rest.Exception.ProtocolResponseException: /token
at com.vmware.horizon.client.rest.Api.getOAuth2AccessTokenByClientCredentials(Api.java:228)

Cause

There is no related OAuth2Client for the Connector worker with an ID of "####" in OAuth2Client vPostgres table.

Resolution

Prerequisite:
Follow KB2149866 to clean up the impacted node.
How to remove a vRealize Automation appliance from a cluster

Identify the Connector ID from the Connector table which is missing an "oAuth2ClientID".

SELECT id, "tenantId", host, "createdDate", "oAuth2ClientId", version FROM saas."Connector";

Delete the Connector by ID that is missing an "oAuth2ClientID" from the Connector table.

DELETE from "Connector" where id=6674;

Remove the impacted Connector from /usr/local/horizon/conf/states/VSPHERE.LOCAL/ directory.

cd /usr/local/horizon/conf/states/VSPHERE.LOCAL
mv 3209 6674 /tmp
mv 3209 6725 /tmp

Reboot all Replica Nodes

On the impacted replica Node, remove the below files

cd /usr/local/horizon/conf/states
rm -r /usr/local/horizon/conf/states
cd /usr/local/horizon/conf/flags
rm sysconfig.firstboot
rm sysconfig.mac_address
rm sysconfig.hostname

Restart the horizon service

service horizon-workspace restart

From the impacted replica node, perform a Cluster Join operation within the vRA VAMI within the Cluster tab.

After the Cluster Join operation completes successfully, confirm that the impacted node has a unique connector ID and a value in the "oAuth2ClientId" table.

SELECT "id", "tenantId", "host", "createdDate", "oAuth2ClientId", "version" FROM saas."Connector";

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
将 CA 签名的 SSL 证书应用于嵌入式 Orchestrator 端口 8283 (71060)

KB
•
移除智能卡时在 Ubuntu 18.4、16.4、SLED12SP3、SLES12SP3 和 SLED11SP4 上自动锁定屏幕 (71068)

KB
•
在启用了 UAC 的 Windows 上无法安装 vRealize Operations Manager 7.5 Telegraf 代理 (70780)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 7.x

Take Our Survey

Support Assistant