Knowledge Base

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

Issues with vCenter Orchestrator permissions (2016770)

Details

Some issues related to access rights occur in vCenter Orchestrator 4.2.1. For example, you might not be able to import workflows or actions as a user without administrative privileges, even if your user role has import permissions. You also might not be able to answer a user interaction in the weboperator Web view as a user without administrative privileges, even if your user role has appropriate permissions.

Solution

To resolve these issues, apply the JAR files attached to this KB article:

  1. Log in as an administrator to the machine on which the Orchestrator server is installed.
  2. Navigate to the Orchestrator server installation folder and replace the o11n-model.jar file with the file attached to this KB in the following locations.
    • If you have installed Orchestrator on a Microsoft Windows machine, navigate to:
      orchestrator_installation_folder\apps\lib\
      orchestrator_installation_folder\app-server\server\vmo\lib\o11n\
      orchestrator_installation_folder\configuration\jetty\lib\ext\
    • If you use the Orchestrator appliance, in the Linux console, navigate to:
      /opt/vmo/app-server/server/vmo/lib/o11n
      /opt/vmo/configuration/jetty/lib/ext
  3. Navigate to the Orchestrator server installation folder and replace the o11n-modelejb-server.jar file with the file attached to this KB in the following location.
    • If you have installed Orchestrator on a Microsoft Windows machine, navigate to:
      orchestrator_installation_folder\app-server\server\vmo\deploy\vmo-server\
    • If you use the Orchestrator appliance, in the Linux console, navigate to:
      /opt/vmo/app-server/server/vmo/deploy/vmo-server
  4. If you use the Orchestrator appliance, verify that the permissions for the files that you replaced are set to 644, and the owner and group are set to vco.
  5. Restart the Orchestrator configuration server:
    a) In the Orchestrator configuration interface, click the Startup Options tab.
    b) Click Restart the vCO configuration server.
  6. Restart the Orchestrator server:
    a) In the Orchestrator configuration interface, click the Startup Options tab.
    b) Click Restart server.

Attachments

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: