merititops
Contributor
Contributor

'Login failed' during plugin setup

Jump to solution

We're testing vCloud and are attempting to use the Orchestrator plugin, we receive an error when connecting to the vCloud host. On Orchestrator Configuration, attempting to add a new vCloud host with shared user credentials results in the following message:

https://vcloud.***.***:443, Login failed with username '***'

(Values changed to protect the guilty)

We've tried both local and LDAP users, "SYSTEM" and normal Organizations, and this is the only result. If we use "Per-user" credentials, everything works fine as long as we use users who are in vCloud. Our Orchestrator & vCloud both pull from the same AD LDAP.

Is this an acceptable install? All of the documentation states not to use per-user credentials.

Thanks.

0 Kudos
1 Solution

Accepted Solutions
Burke-
VMware Employee
VMware Employee

This most likely has to do with DNS resolution (forward/reverse lookups).. Try changing the plugin to use the IP Address of your vCloud Director server instead of the FQDN. That is only a workaround.. the fix will be to resolve the DNS issues.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter

View solution in original post

0 Kudos
2 Replies
Burke-
VMware Employee
VMware Employee

This most likely has to do with DNS resolution (forward/reverse lookups).. Try changing the plugin to use the IP Address of your vCloud Director server instead of the FQDN. That is only a workaround.. the fix will be to resolve the DNS issues.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter

View solution in original post

0 Kudos
merititops
Contributor
Contributor

Thanks for the tip, this did the trick, and oddly fixed whatever problem was occuring. Changed to the IP addresses and it worked, then went back and tried the DNS name again, and that worked too. Must've been a caching issue or something.

Thanks!

0 Kudos