You need to authorise before making the call, see my VSphere Automation SDKs, PowerShell And You – Part 1 post.
I just added function Get-rProxyConfig and updated Sample1.
See Sample1 in my OpenSdk repo.
Sample output from my test system with no proxy configured.Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz1 person found this helpful
Thanks LucD. Isn't the point of "connect-cisserver" to authorize my connection to the VAMI REST API? I was hoping to avoid making something custom, although if that's what I'm going to need to do so be it.
Thanks for the proxy output, seems I was on the right track, just needed to get past the authorization problem.
I see where my issue is now. I was so focused on just changing the proxy config, that I assumed that I should be authenticating against the 'VAMI' REST API as the VCSA local root user. Which, by the way, authenticates just fine, but does not seem to grant any worthwhile access. I had to authenticate using my SSO admin account.