VMWare credential Test Failure

[DuaneNMore]

I have 2 VMWare credentials, one was used with an old discovery solution, the other is to be used with ServiceNow Discovery. Lets call them oldvmwarecred and newvmwarecred; the server we are attempting to test the cred against vserver.

I have set midserver mid.log.level to debug.

I can navigate to https://vserver and log in with either oldvmwarecred or newvmwarecred successfully from the MID Server doing the work to ensure no firewall issues.

When I execute a test credential using oldvmwarecred it returns with credential validated, In the Mid Server log I see an COmmandPipeline entry for VMWareConnectionFactory in the agentlog which appears to be associated with this execution.

When I execute a test credential using newvmwarecred it returns with "null". I don't see a similar CommandPipeline entry for the "VMWareConnectionFactory" in the agentlog.

We are being required to change the credentials when going from one discovery product to the other by information security for non-repudiation purposes, so using the old cred isn't going to work.

This behavior occurs both in instanbul patch0 and patch3

[tphillips]

Are both credentials in the form of userid@vshpere.local or something similar?  

Tom

[DuaneNMore]

I found that it was a permission issue with having access to the SDK on the vCenter   appliance. It now works.