You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connects to the vRA Server (and either successfully authenticates or fails with invalid credentials)
Actual behavior
HTTP 400 Bad Request error
I believe this is because Connect-vRAServer uses the endpoint /csp/gateway/am/idp/auth/login?access_token which was deprecated in a recent version and as of v8.12 has been removed completely, thus completely breaking PowervRA user/pass credential authentication.
Rather, line 165 needs to instead use endpoint /csp/gateway/am/api/login?access_token
Environment data
>$PSVersionTable
Name Value
---------
PSVersion 5.1.17763.3770
PSEdition Desktop
PSCompatibleVersions {1.0,2.0,3.0,4.0...}
BuildVersion 10.0.17763.3770
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1# as well as >$PSVersionTable
Name Value
---------
PSVersion 7.3.4
PSEdition Core
GitCommitId 7.3.4
OS Microsoft Windows 10.0.17763
Platform Win32NT
PSCompatibleVersions {1.0,2.0,3.0,4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0> (Get-Module PowervRA).Version
Major Minor Build Revision
-----------------------520-1>$vRAConnection# N/A
The text was updated successfully, but these errors were encountered:
tocano33
pushed a commit
to tocano33/PowervRA
that referenced
this issue
May 31, 2023
Steps to reproduce
Connect-vRAServer -Server [server] -Credential (Get-Credential)
Expected behavior
Connects to the vRA Server (and either successfully authenticates or fails with invalid credentials)
Actual behavior
HTTP 400 Bad Request error
I believe this is because Connect-vRAServer uses the endpoint
/csp/gateway/am/idp/auth/login?access_token
which was deprecated in a recent version and as of v8.12 has been removed completely, thus completely breaking PowervRA user/pass credential authentication.Rather, line 165 needs to instead use endpoint
/csp/gateway/am/api/login?access_token
Environment data
The text was updated successfully, but these errors were encountered: