vRealize Orchestrator 7 - issue SSO

Similar Questions

• Issue by the way CHIEF: ChefHost Chief Workflow parameter in vRealize Orchestrator API

  I have an environment with vRealize Orchestrator with CHIEF plugin installed. I want to call the API to initiate a workflow LEADER in vRealize Orchestrator.

  I want to call the workflow MANAGER Add New Role . The input parameters for this workflow are

  <input-parameters> 
       <parameter description="Chef Server" type="CHEF:ChefHost" name="host"/> 
       <parameter description="Name of new role" type="string" name="role"/> 
       <parameter description="(Optional) Description of new role" type="string" name="description"/> 
  </input-parameters>
  

  The format for sending the parameters of the form type="string" is

  In JSON

           

  {
       "value":{"string":{"value": "role name"}},
       "type": "string",
       "name": "role"
  }
  

  In XML

  <execution-context xmlns="http://www.vmware.com/vco">
    <parameters>
         <parameter name="role" type="string">
              <string>Role Name</string>
         </parameter>
    </parameters>
  </execution-context>

           

  The problem, I do face is with the parameter type="CHEF:ChefHost" . I can't get the correct syntax for the shipment of type = "CHIEF: ChefHost '. During the test with the factor, I always get a 400 error with descriptionThe request sent by the client was syntactically incorrect.

  Is there a document that shows how to create a CHEF:ChefHost type?

  PS: I asked this question in http://stackoverflow.com/questions/37405901/issue-in-passing-chefchefhost-parameter-for-chef-workflow-in-vrealize-orches...

  Because I don't have an answer of SO, I ask you here.

  Chief Guest, as any other plugin object are passed as objects sdk-object are identified uniquely by their type and the id attributes. Here's how the body of the request should look like:

  in XML:

  in JSON:

  {
    "parameters" : [
      {"value":{"sdk-object":{"type":"Chef:Host","id":"b0c408c4-1d85-4a97-9314-727552fd5a39"}},"type":"Chef:Host","name":"host"}
    ]
  }
  

  You need to replace the id attribute in applications above with the current host id. To find the real ID of your host, you can query vRO catalog REST API - /GET https://{vro-host-or-ip}:8281/vco/api/catalog/Chef/Host

  In the returned response, find your host data, get the value of the dunesId attribute (must be a GUID string) and use it as a value for the id attribute in applications above.

• vRealize Orchestrator stock adapter for vCops

  I wanted to reach out and see if someone of you all use the vRealize Orchestrator stock adapter for the vRO living vCops and vCops.  vRO 6.0.3 works out of the box with this solution, but I am fighting to get vRO7 to work and are passed to the 'cannot find getvcuuid workflow, full authentication required.

  Any person using this solution with vRO7 and if so how did you fact to work?

  Thank you

  Steve

  Hi Steve,.

  I'm not using this card, but I've seen similar errors on full authentication is required in environments where:

  • vRO is configured with LDAP authentication not; That is to say. SSO or vIDM
  • the client code attempts to call the vRO REST API using Basic authentication via user/password name.

  If your setting of the vRO 7 corresponds to these conditions, pourriez you open the /etc/vco/app-server/vmo.properties file and check if there is a property named com.vmware.o11n.sso.basic - authentication.enabled? This property is required for basic authentication work on SSO/vIDM

  So, if your do not have this property, could you add the following line to the /etc/vco/app-server/vmo.properties file, restart the server from vRO (vco-Server service restart) and check if the adapter works now?

  com.vmware.o11n.sso.basic-authentication.enabled=true
  

• vRealize 7 - NSX Automation deployments fail due to problems of certificate with vRealize Orchestrator

  Hello community,

  After you have installed the latest version of vRA, vRO, and NSX I run questions when you apply components that use components of the NSX. First of all: details of the version:

  -vRA: 7.0.0 (build 3292778)

  -vRO: 7.0.0.16989 (build 331003)

  -NSX: 6.2.1 (build 3300239)

  vRO plugin versions are delivered with the vRO version listed above with the exception of the plugin NSX, which has been updated to the latest version (1.0.3 published on 17.12.15).

  In the configured tenant vRO is configured as endpoint. I can check the data collection is running and working. I can see the plugin NSX for vRO runs the workflow 'create endpoint NSX' from time to time using the configured user of vRA VRO.

  In the configured tenant vRO is thus configured as server default for ASD vRO. Connection test is successful. When you save the config I'm prompted to approve the vRO certificate, which I confirm. Note that the thumbprint specified matches the footprint of the vRO certificate that I get during the visit of the vRO system on https://vro:8281. I am able to navigate the vRO vRA designer workflows, therefore: connection seems established.

  Within vRO the vRA COFFEE and plug-ins IAAS have been saved successfully. I am able to browse the inventory of plugin for both plugins.

  To solve the problem, I created a new unified plan within the design section of vRA with the following configuration:

  -Transport box: my area of transport configured NSX (checked: manual creation on this area using NSX works very well)

  -Routed res pol. Bridge: my reference for the dash cluster to use Pol

  -The only component dragged to canvas is a 'network and safety'-> 'On-Demand NAT Network' that uses a profile preset 1-to-many network as is "Parent network profile" without manual modification.

  -Note that, although there is a plan very simple example to illustrate the problem, it happens with any model that I have set up if any component is confgured requiring the NSX plugin for vRO.

  "Whenever I ask this plan, the request fails with the error message:" ","application [fa1e0689-0d06-4308-a914-e498c0d1fd99]: 404 not found "

  Looking in vCenter, NSX and vRO I can check that nothing is really trigged when you ask for the action plan.

  Consider the vRA /storage/log/vmware/vcac/catalina.log becomes very visible:

  com.vmware.vcac.iaas.vco.network.helper.VcoEndpointSelector.isEndpointAlive:88 -
  vRealize Orchestrator endpoint with url [https://s00-vro.my.domain:8281/vco] is not alive. 
  Exception message:> [Host name 's00-vro.my.domain' does not match the certificate subject provided by the peer (CN=s00-vro.my.domain, OU=VMware, O=My Company, C=DE)]
  
  com.vmware.vcac.iaas.vco.network.helper.VcoEndpointSelector.getFirstAliveEndpointByPriority:200
  - vRealize Orchestrator endpoint [https://s00-vro.my.domain:8281/vco] with priority 1 is not alive. Skipping.
  
  org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolv
  er.logException:189 - Handler execution resulted in exception: Endpoint not found. There are no vRealize Orchestrator endpoints that are alive.
  
  com.vmware.vcac.platform.service.rest.resolver.ApplicationExceptionHandler.handleHttpStatusCodeException:673 - 404 Not Found
  org.springframework.web.client.HttpClientErrorException: 404 Not Found
  ...
  ...
  ...
  
  

  Please note that I double checked the certificate. This is a self-signed certificate created using the 7.0 vRO new control panel, the one I get when you go to https://vro:8281. It is valid and the object (issed to CN) matches perfectly the hostname entered the ASD and endpoint configuration in the vRA. It is separable and time on all components of the server is in sync with the use NTP.

  Now, I even re-generated certificate and re-registered and rebooted all the components, but while I can see that the certificate has been updated all components I always get the same question.

  Never had this problem with the previous version of the NSX / vRA / vRO. I checked the documentation if nothing has changed here, but did not find what I'm doing wrong. Anythimg I'm missing here? Any bug?

  OK, this seems to be the issue. So put atleast to previous day since version ofvRO (cannot check if it's true for charges vRO 7 installs as well but it is probably) vRO 'control center' will generate certificates based SHA1 vRA love not for actions that use the endpoint in the vRA vRO. ASD seems to work without these problems.

  Sidenote: VRO upgraded installs will also come with SHA1 based CERT if they use a self-signed cert created by vRO. However: you would think that it is sufficient to recreate the cert using the control center. But it turns out it isn't, because it will generate a (new) based SHA1 cert.

  What I did to solve the problem:

  1. create a vRO SSH2 based certificate without the cert extensions, similar to the one that ships with built-in vRA vRO. I tend to use xCA for these jobs, but openSSL will do as well. The exact format required for the certificate of vRO is not documented, but I can make sure you need it like this: PEM certificate in key private and public including format PKCS #1, formatted as follows:

  -----BEGIN RSA PRIVATE KEY-----
  (Your private Key: your_vro_server.key)
  -----END RSA PRIVATE KEY-----
  -----BEGIN CERTIFICATE-----
  (Your primary certificate: your_vro_server.crt)
  -----END CERTIFICATE-----
  -----BEGIN CERTIFICATE-----
  (Your intermediate certificate: intermed.crt)
  -----END CERTIFICATE-----
  -----BEGIN CERTIFICATE-----
  (Your root certificate: root.crt)
  -----END CERTIFICATE-----
  

  I had problems when I used the key extensions so I would say you don't use and don't create a very basic cert without extensions V3, as indicated on the right of the image to my last post (ideally, you want to have a cert with the same properties as the cert is used by the device of integrated vRO vRA unless of course different CN) etc.).

  2. use the vRO control center located at https://your-externa-vro:8283 / vco-controlcenter / #/ and move to--> Orchestrator Server SSL certificate certificates. Use the action to import to import your PEM cert. It should tell you that you need to restart your device vRO. Then RESTART the device (for not just restart the service, this seems not be sufficient).

  3 al ' vRA remove the Endpoint vRO everywhere wherever it has been configured. Also, I removed the vRO to the ASD config just to make sure that nothings left.

  4 reboot the vRA power (IAAS can be left as what). I needed to do this because I have seen that the keystore at some point would keep beeing crushed by CERT vRA (?), I deleted it (AND I checked that they are deleted) reappears in the keystore after a while. After a reboot, the problem was gone, the keystore was clean.

  5. Add the configuration of endpoint and ASD vRO. Accept the certificate.

  6. the works.

  Therefore, while I have no more time to solve the problems more than I guess the problem is the SHA1 function certificate generated by the device of vRO. The internal unit is equipped with a SHA2 based cert that works and after that change the external device SHA1 cert in a basic cert SHA2 all works.

• vRealize Orchestrator - cannot add to vSphere Web Client

  Hello

  I configured the device vRealize Orchestrator and added the vCenter Server to the server via the customer to vRO Orchestrator--> library and can successfully run workflows against objects in vCenter. Then vRO works.

  BUT

  The problem I have is that I can't seem to add the server vRO to vSphere Web Client. I do not see the plugin if and when I go to the Orchestrator plugin I see the vCenter Server in the "House of vCO' tab but"N/A"under"Managed by vCenter Orchestrator Server"." Under the "Lists" section it says "vCO servers: 0".» What Miss me?

  I tried to add the new server to vRO (device) by changing the vCenter object and enter the server IP new vRO. But "Test connection" fails every time.

  In addition, vCO has been installed with vCenter initially but never used and not yet used. But I don't think it would make a difference.

  I don't see the vCenter plugin tab in the left menu when connecting to vRO with the customer and com.vmware.vco isn't showing in /mob .

  Versions:

  vCenter: 5.5u2

  vRO: 6.0.3.0 build 3000579

  Thank you!

  Hello

  I'm a bit confused. It seems you are trying to use the two vCO 5.5.2 and vRO with VC 5.5.2 6.0.3, but plug-ins are different (they have different deployment mechanism, different extensions in MOB, etc.). I recommend you stick to the version of the vCO you got installed with VC - in this case, 5.5.2.

  Then, check the following:

  • Check that the vCO is configured with the SSO authentication, and it is the same instance used by VC/Web Client SSO
  • Check that this instance of vCenter is added as properly to vCO and there is an extension of 5.5.x - style into the CROWD. His name is com.vmware.orchestrator. [some-guid]
  • Check that the extension of the server property contains a record with URL property pointing to the server fine vCO - https:[vco-ip]:8281
  • Make sure that the user you are using to connect to the Web Client has a permission; for example. You should be able to connect to vCO Client Java with this user

  If the foregoing is valid, check the Web Client (vsphere_client_virgo.log) log file for any errors of loading of the vCO and connection at the vRO server plugin.

• How do I send vRealize Orchestrator events to another monitoring tool

  I would like to send the vRealize Orchestrator events to another tool (connector BSM). Can achieve us through the following methods,

  1] send vRealize Orchestrator as interruptions snmp events to the BSM connector

  can [2] I send events directly to the connector by agent.

  Please tell me which is the best approach.

  Official documentation is quite lite: generic SNMP request Workflows

  But, I can confirm that there is a simple workflow 'Send a SNMP trap' as part of the library:

  

  I even recorded a video as an example of use of workflow that was part of a class that I used to teach a few years ago:

  Execution of workflow and trap to send fail - YouTube

  That should help...

• Impossible to connect to new vRealize Orchestrator install

  Hey all, I installed vRealize Orchestrator and has not been able to enter the correct credentials. I tried using the root login and password during installation, I created and I tried to use my credentials for vCenter (format username@domain both user domain\username) but no joy. I get the "" connection failed: incompatibility of the username/password or account temporarily blocked after too many failed attempts "error message." I think I've tried four times; How many times are too many failed attempts?  I checked in vCenter and my vCenter admin account was listed under > manage > permissions for vRealize. I was skeptical that I had incorrectly entered the root password but I thought I would give it another try so I did a nuke and repopulate and tried again. No, I still can't with the credentials that I created or my credentials for vCenter. "Installation and Configuration Guide" is not much help here.

  I'm trying to install VMware-vRealizeOrchestrator-Unit - 6.0.4.0 - 3619080_OVF10.ova in VMware vCenter 6 Standard. Am I missing a step somewhere that will help me to access and configure my vRealize Orchestrator?

  Thank you

  Joe B

  Hey Joe,

  Where exactly you are trying to connect with the root account? Client Java vRO, or in the vRO Web Configurator, or elsewhere?

  By default, vRO is configured with LDAP authentication, integrated, to connect with the vRO Java client, you will need to use some of the embedded LDAP user accounts (IE. ( vcoadmin). For the Web Configurator, I think the default user name is vmware. The root account is if you want the SSH connection at the vRO device.

• vRealize Orchestrator - ovfManager.parseDescriptor return error

  Hello

  I intend to write a script in vRealize Orchestrator to import an OVF. For this, I started with the script and wrote up to present this and it works to take one step at a time. But I get the error message "TypeError: cannot call the method"parseDescriptor' null ' for the parseDecriptor function "I added System.log (ovfD) to print the happy POC check and it prints.» So still I don't know why he gives me this. Am I missing something here?

  var ovfmanager = host.sdkConnection.ovfManager ();

  var descriptorSpec = new VcOvfParseDescriptorParams();

  descriptorSpec.locale = ";

  descriptorSpec.deploymentOption = ";

  tempDir var = System.getTempDirectory ();

  fileReader var = new FileReader (tempDir + ' / ss.ovf');

  fileReader.open ();

  var ovfDescriptor = fileReader.readAll ();

  var ovfD = String (ovfDescriptor);

  ovfD = ovfD.trim ();

  fileReader.close ();

  System.log (ovfD);

  var ovfInfo = ovfmanager.parseDescriptor (ovfD, descriptorSpec);

  On the first line, you try to run an ovfManager() method, but this is not a method; It is a property.

  The first line must therefore

  var ovfmanager = host.sdkConnection.ovfManager;
  

• vRealize Orchestrator 6.0.3 with VCSA 6.0 U1a

  I tried to deploy vRealize Orchestrator 6.0.3 with my instance VCSA 6.0 U1 (supported by the compatibility matrix), the symptoms are almost exactly the same as this post:

  Re: Installation of vRO v6.01 but not displayed in the web client

  Can run workflows, auth using the client, everything, just no plugin in the web client.

  com VMware.VCO does not at all appear in the browser MOB however.

  I tried the cat-ing, the file virgo.log on the VCSA, but nothing for vco-plugin returns when I say vro to save the extension with vcenter.

  All that shows in the web client is started page, nothing else - I tried to restart the WebClient service and device, also restart the vro device - nothing works.

  It drives me crazy, nobody knows what about this problem?

  Myles

  A market:

  http://Orchestration.IO/2015/09/28/deploying-vrealize-Orchestrator-6-0-3/

  When you run the registry extension to vCenter workflow, I was specifying only vro1.lab.mylesgray.io, not: https://vro1.lab.mylesgray.io:8281 as it should be.

  Also, it fails when configuring Configuration Manager, so I guess it just specifies the domain also FULL name and not the Protocol and port.

• Missing plug-ins and custom after the vRealize Orchestrator restart code

  We had power outage and vRealize Orchestrator server has been restarted. All plug-ins installed and work/actions/configurations custom flow shortage now. Please see the image attached to the current state of the workflow library tree. Unfortunately, we didn't save the work anywhere elsewhere. How can we recover the missing items?

  Orchestrator appliance is equipped with a local PostgreSQL database by default. He started working as expected after changing the type of database shipped for PostgreSQL database. I don't know yet why it has been reset to the database incorporated after the reboot.

• Where is vRealize Orchestrator 6.0?

  We want to upgrade to vRealize Autoamtion 6.2.

  A condition for this is the vCAC 6.2 for vCO plugin.

  This plugin requires vRealize Orchestrator 6.0 which should be available since December 9. 2014

  See also the release notes for the plugin:

  https://www.VMware.com/support/Orchestrator/doc/Vcac-plugin-62-release-notes.html

  VMware vRealize Orchestrator 6.0.0 (formerly vCenter Orchestrator) | December 9, 2014 | Generation 2289455

  Unfortunately I find anywhere vRealize Orchestrator 6.0 for download on the VMware page.

  Sounds like a question of upgrading chicken egg to vCAC (vRealize Automation) 6.2

  Someone at - he saw vCO 6.0?

  Regards, Sven

  external device vRO is now available to customers saving a request supported by this Article KB

• How to install vrealize orchestrator?

  How can I install the vrealize of the iso vcenter Orchestrator 6?

  I don't think the vRO Setup is on the iso vCenter more since version 6, because the windows installation has been deprecated.

  You can download and deploy the vRO in the form of separate appliance of the download of myvmware for vSphere page 6.

  Kind regards

  Joerg

• 5.1 to 5.5 upgrade issue SSO

  I'm considering upgrading to a 5.1 U2 (Vcenter) hosts are 5.5 U2 U3. When I installed SSO in 5.1, I chose a multisite installation.

  I am considering using the bound mode but have since then decide not to do so. Can I change to a basic SSO installation when you perform an upgrade or do I need to do a fresh install to achieve?

  Unfortunately, the SSO Upgrade Wizard does you not an option to change the mode of SSO deployment during the upgrade process. When you run the Setup program, it automatically detects the mode of deployment and SSO version installed on the machine and it will go ahead and update SSO for you.

  So to answer your question, if you want to change the mode of deployment of SSO, you must uninstall SSO 5.1 and install SSO 5.5 U2 with Standalone SSO mode.

• How can I change the font size on vRealize Orchestrator Client?

  Hello

  There is no way to change the size of the font of the interface client vRO?

  Change of DPI in windows has no effect on the client.

  Thank you

  Hello

  Sorry, size of the police (and other Visual parameters) in customer vRO are not configurable.

• Criteria for inclusion of workflow via vRealize orchestrator

  Hi all

  I tried to get the workflow 'Register a subscription to workflow system' to work. Subscription seems to work very well, but I can't come up with syntax for part of criteria, if some of you could share this information. Should be defined what it if I would get the trigger to the State:

  phase: PRE

  State: VMPSMasterWorkflow32.Requested

  payload > lifecycleState > phase: PRE
  payload > lifecycleState > State: VMPSMasterWorkflow32.Requested

  M

  Of course, no prob.  Here is the code that contains a script that I use to create criteria for underwriting for machine type = VM, the dimensioning of the machine and the phase POST:

  var provisioningCriteriaObj = {}

  'type': 'and',

  "Paragraphs": [{}

  "type': 'expression."

  'operator': {}

  'type': ' equal to '.

  },

  'leftOperand': {}

  "type': 'path."

  "path": "data ~ machine ~ type.

  },

  'rightOperand': {}

  "type': 'constant."

  'value': {}

  "type': 'integer."

  'value': 0

  }

  }

  }, {

  "type': 'expression."

  'operator': {}

  'type': ' equal to '.

  },

  'leftOperand': {}

  "type': 'path."

  "path": "data ~ lifecycleState ~ State."

  },

  'rightOperand': {}

  "type': 'constant."

  'value': {}

  "type": "string",.

  'value': 'VMPSMasterWorkflow32.MachineProvisioned '.

  }

  }

  }, {

  "type': 'expression."

  'operator': {}

  'type': ' equal to '.

  },

  'leftOperand': {}

  "type': 'path."

  "path": "data ~ lifecycleState ~ phase."

  },

  'rightOperand': {}

  "type': 'constant."

  'value': {}

  "type": "string",.

  'value': 'POST'

  }

  }

  } ]

  };

  provisioningCriteria = JSON.stringify (provisioningCriteriaObj);