WebApp SSL binding bug

[hovsepm]

From @j055 on August 31, 2017 14:2

#2935 - No update since June but this is still an issue in the latest release v1.2.

I've tested in a new web app with certificate installed. The certificate binding is not added.

           _webApp.Update()
                .WithClientCertEnabled(true)
                .DefineHostnameBinding()
                .WithThirdPartyDomain(domain)
                .WithSubDomain(subDomain)
                .WithDnsRecordType(CustomHostNameDnsRecordType.CName)
                .Attach()
                .Apply();

The API doesn't allow specifying IP or SNI and I have no idea why WithClientCertEnabled(true) is stuck there.

A better way might be:

            _webApp.Update()
                .DefineSslBinding()
                .ForHostname(domain)
                .WithExistingCertificate(thumbprint)
                .WithSniBasedSsl()
                .Attach()
                .Apply();

Thanks
Andrew

Copied from original issue: Azure/azure-sdk-for-net#3643

[martinsawicki]

it looks like we missed porting .withExistingCertificate() on the Update chain to .NET...
we'll try to squeeze it into v1.4

[yaohaizh]

@xccc-smft, @ChenTanyi , do you know whether we fix this issue recently?