Closed nmallick1 closed 6 years ago
@ahmedelnably @panchagnula Can one of you take a look at this issue? Thanks.
@nmallick1 Can you try this with the latest version of AzureRM modules?
@nmallick1 : Webspaces is not a concept that we expose to on our API level so we never use this property on CLI or PS - so this should be something the API should handle or at least, there should be someother property we might be missing here to set, but webspace is not something we will be able to set from OS, I am closing this - since we cannot fix this. If this is not an API level issue & we need to make some changes (like set some other property so that the API works correctly) then please file a new issue. Thank you.
@Sisira Panchagnulamailto:sisirap@microsoft.com The property we miss adding is the HostingEnvironmentProfile within the properties of the certificate PUT call. If the HostingEnvironmentProfile is present then the webspace is properly assigned by the backend API.
I actually wanted to request a means to specify the HostingEnvironmentProfile in this cmdlet.
From: Sisira Panchagnula notifications@github.com Sent: Friday, October 12, 2018 4:46 PM To: Azure/azure-powershell Cc: Nazeef Mallick; Mention Subject: Re: [Azure/azure-powershell] New-AzureRmWebAppSSLBinding when used with -CertificateFilePath on ASE uploads the certificate to incorrect webspace (#7537)
@nmallick1https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnmallick1&data=02%7C01%7Cnmallick%40microsoft.com%7C8a8a33a4b3024f8f76e608d6309ce6a3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636749847828227783&sdata=ewj8EOhuyvir9sPgHSbmvvLo%2BXJnc9Trvj8K%2FiGfZ8E%3D&reserved=0 : Webspaces is not a concept that we expose to on our API level so we never use this property on CLI or PS - so this should be something the API should handle or at least, there should be someother property we might be missing here to set, but webspace is not something we will be able to set from OS, I am closing this - since we cannot fix this. If this is not an API level issue & we need to make some changes (like set some other property so that the API works correctly) then please file a new issue. Thank you.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-powershell%2Fissues%2F7537%23issuecomment-429490925&data=02%7C01%7Cnmallick%40microsoft.com%7C8a8a33a4b3024f8f76e608d6309ce6a3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636749847828227783&sdata=sleZsxGCcbaHsYcU9ewAtacBWUO9oGikWGbyZkoha58%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUBiSX-4NkJdDpLXKJx-1CCAUvEQ8E2Aks5ukSnHgaJpZM4XaSSa&data=02%7C01%7Cnmallick%40microsoft.com%7C8a8a33a4b3024f8f76e608d6309ce6a3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636749847828227783&sdata=%2FzTFBtU2Y0cbj8FIXiq39KPYZtN1QECshVgzXiv%2FgXI%3D&reserved=0.
Description
Using New-AzureRmWebAppSSLBinding against a site hosted on an App Service Environment (ASE) along with -CertificateFilePath parameter to upload the certificate as well, causes the certificate to be uploaded in incorrect webspace. This subsequently causes the binding assignment to fail. New-AzureRmWebAppSSLBinding does not take the HostingEnvironmentProfile into consideration. The resulting webspace does not have ASE name appended to it.
Script/Steps for Reproduction
New-AzureRmWebAppSSLBinding -ResourceGroupName "<>" -WebAppName "<>" -Name "<>" -CertificatePassword "**" -CertificateFilePath "COMPLETE_PFX_FILE_PATH"
Module Version
Environment Data