Editing a Directory in vRA fails with error "Could not resolve domains"
search cancel

Editing a Directory in vRA fails with error "Could not resolve domains"

book

Article ID: 325858

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
Editing a Directory in vRA fails with error "Could not resolve domains"

In /var/log/vmware/horizon/connector.log you see the error:

2018-10-16 15:25:02,845 ERROR (SimpleAsyncTaskExecutor-5) [[email protected];[email protected];127.0.0.1] com.vmware.horizon.directory.ldap.DirectoryHostResolutionService - Error obtaining host information using SRV, falling back to not using SRV if it is not configured
2018-10-16 15:25:02,845 ERROR (SimpleAsyncTaskExecutor-5) [[email protected];[email protected];127.0.0.1] com.vmware.horizon.directory.ldap.DirectoryHostResolutionService - com.vmware.horizon.directory.DirectoryServiceException: Authentication failed for the given user using authentication mechanism - GSSAPI
2018-10-16 15:25:02,845 ERROR (tomcat-http--60) [[email protected];[email protected];127.0.0.1] com.vmware.horizon.directory.ldap.LdapCrossRefService - Unresolvable host and port for cross ref object for -  DOMAIN.LOCAL


Environment

VMware vRealize Automation 7.x

Cause

The Domain can not be resolved, this can be due to missing configuration or a duplicate krb5.conf file.

Resolution

To resolve this issue:
For vRA the krb5.conf should be only located in /etc/krb5.conf. If you find the file in /usr/java/jre-vmware/lib/security/krb5.conf then please move it to a different location.
The file /usr/java/jre-vmware/lib/security/krb5.conf might have been setup to configure vRO for PowerShell as part of Configure Kerberos Authentication