Search the VMware Knowledge Base (KB)
View by Article ID

How to use JXplorer to update the LDAP string for an identity source for vRA 6.0.x, 6.1.x (2077170)

  • 3 Ratings

Purpose

LDAP strings are not editable in vRealize Automation (formerly known as vCloud Automation Center)6.0/6.0.1 once you have created the Identity Store.
This article describes how to use JXplorer to update the string and how to add a global catalog port to the address to increase the speed of LDAP searches.

Note: This edit is not required for vRealize Automation 6.2.x versions as you are able to modify the LDAP string directly from Tenants.

Resolution

To update the LDAP string for an identity source for vRA using JXplorer:
 
  1. Before you make any changes to the Identity or SSO server, backup the virtual machine and the associated database.
  2. Install JXplorer from this link:
    http://jxplorer.org/downloads/
  3. After you have installed JXplorer, you need to configure your connection to the vRealize Automation Identity Server, or vCenter Server SSO.

To configure the connection:

  1. Open a new connection.
  2. For host, enter the FQDN of your vRealize Automation Identity or SSO Server.
    • The protocol is LDAP v3.
    • Base DN will be dc=vsphere,dc=local.
    • The Security Level will be User + Password.
    • The Security User DN will be  cn=administrator,cn=users,dc=vsphere,dc=local.
    • The Security Password will be your administrator password for the Identity or SSO sever.
Connect to the Identity or SSO server and expand/navigate to these locations in the tree:
  • local
  • vsphere
  • Services
  • IdentityManager
  • Tenants
  • (The Domain you want to change or update)
  • Identity Providers
  • Select the domain
To make the changes to the LDAP string:
  1. Change from the HTML view tab to the Table Editor tab.
  2. Edit the vmwSTSConnectionStrings to make the changes. For example, you can change ldap://domain.com to ldap://domain.com:3268.
  3. Click Submit.
  4. Refresh the tree or domain on which you are to confirm that the change has taken effect.
Note: There is no need to restart any vRealize Automation Servers to allow this change to take effect.

Additional Information

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 3 Ratings
Actions
KB: