The following error occurs when running Set-MgmtSvcRelyingPartySettings command from WAP deployment guide, page 15, step 22:
PS C:\Windows\system32> Set-MgmtSvcRelyingPartySettings -Target @('Admin', 'Tenant') -MetadataEndpoint https://WAP-APS:4486/wap/metadata.xml -ConnectionString $cnctString -DisableCertificateValidation Set-MgmtSvcRelyingPartySettings : The underlying connection was closed: An unexpected error occurred on a send. At line:1 char:1 + Set-MgmtSvcRelyingPartySettings -Target @('Admin', 'Tenant') -MetadataEndpoint h ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Set-MgmtSvcRelyingPartySettings], WebException + FullyQualifiedErrorId : System.Net.WebException,Microsoft.WindowsAzure.Config.PowerShell.Claims.SetRelyingPartySettings
Incorrect certificate was generated while following previous steps of WAP deployment guide (Section 3, steps 12-25)
Check that XML
https://WAP-APS:4486/wap/metadata.xml is returned correctly when opening it on WAP node. If XML is not accessible using https, but is accessible using http, then most likely the certificate was incorrectly generated at the step 10 of WAP Deployment Guide (section 3: Configure Windows Azure Pack). For example, "CN=WAP-APS,O=Parallels,C=RU" in the command was replaced with some other data. To fix the error, please go back to the step 10 and repeat all further steps of this section.
Please note that it is necessary to use the same hostname for POA MN while running all commands from the section 3. So if WAP-APS was used in the command:
/usr/java/default/bin/keytool -genkeypair -alias wap -keystore /usr/local/share/WAP/WAPKeyStore -keyalg RSA -keysize 2048 -validity 3650 -storepass '<Password>' -keypass '<Password>' -dname "CN=WAP-APS,O=Parallels,C=RU"
then it should be used in all commands at the step 25. If another hostname hostname.tld was used in keytool command, it should be used in *all other commands where WAP-APS is mentioned in WAP Deployment Guide.