sso_resource_uri

[npeletisgen]

Does your code for getting the sso_url still work?
I'm able to kick off the POST on the job template and retrieve the resource uri but the following GET request to that resource uri to obtain the actual SSO URL returns a failure {"detail":"Not Found"}

$_resp = Invoke-HPECOMWebRequest -Region $Region -Uri $Uri -Method POST -body $payload -ContentType "application/json" -WhatIfBoolean $WhatIf
                    
                    [{0}] Running Wait-HPECOMJobComplete -Region '{1}' -Job '{2}' -Timeout '{3}'" -f $MyInvocation.InvocationName.ToString().ToUpper(), $Region, ($_resp.resourceuri), $Timeout | Write-Verbose
            
                    if (-not $Whatif) {

                        $_resp = Wait-HPECOMJobComplete -Region $Region -Job $_resp.resourceuri -Timeout 20 
                        
                        "[{0}] Response returned: `n{1}" -f $MyInvocation.InvocationName.ToString().ToUpper(), $_resp | Write-Verbose
                        
                        $ssoResourceUri = $_resp.statusDetails.sso_resource_uri
                        
                        "[{0}] ssoResourceUri returned: {1}" -f $MyInvocation.InvocationName.ToString().ToUpper(), $ssoResourceUri | Write-Verbose
                        
                        $ssoUrlContent = Invoke-HPECOMWebRequest -Region $Region -Uri $ssoResourceUri -Method GET 
                        
                        $ssoUrl = $ssoUrlContent.sso_url

[jullienl]

No, it doesn't. This is due to the new HPE GreenLake endpoints that I'm now using in the library following the deprecation of the previous ones. I'm currently in discussions with the HPE GreenLake team to resolve this issue.

[jullienl]

This issue is scheduled to be resolved in version 1.0.16, which will be released soon.