Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Registering vCenter Orchestrator with a vCenter Single Sign On server which contains a large number of groups might cause issues (2039478)

Details

If you configure Orchestrator to use vCenter Single Sign On authentication and register the Orchestrator server with a vCenter Single Sign On server which contains a large number of groups, a timeout might occur when the list of groups is loaded. The Orchestrator configuration interface might become unresponsive and you might receive an out of memory error message.

Solution

Edit the sso.properties file, which is created when you register the Orchestrator server with a vCenter Single Sign On server.

  1. Navigate to the correct folder on the Orchestrator server system:
    OptionAction
    If you installed Orchestrator with the vCenter Server installerGo to install_directory\VMware\Infrastructure\Orchestrator\app-server\server\vmo\conf.
    If you installed the standalone version of OrchestratorGo to install_directory\VMware\Orchestrator\app-server\server\vmo\conf.
    If you installed the Orchestrator ApplianceGo to /opt/vmo/app-server/server/vmo/conf.


  2. Open the sso.properties configuration file in a text editor.
  3. Add the following lines to set your domain and admin group:

    com.vmware.o11n.sso.admin.group.domain=your_domain
    com.vmware.o11n.sso.admin.group.name=your_admin_group

  4. Replace this line

    com.vmware.o11n.sso.install.state=registered

    with

    com.vmware.o11n.sso.install.state=approved


  5. Save the sso.properties file.
  6. Start or restart the Orchestrator server.

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

  • 0 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)
  • 0 Ratings
Actions
KB: