Skip to content

BUG in SSL certificates assignment to bindings #332

Description

@konste

Repro:

$BindingInfo = @(
    New-CimInstance -ClassName MSFT_xWebBindingInformation -Namespace root/microsoft/Windows/DesiredStateConfiguration -Property @{
        Protocol              = 'https'
        IPAddress             = '*'
        Port                  = 443
        HostName              = 'api.bittitan.com'
        CertificateThumbprint = '34AE59F4CFA28602716C46D172850747B36624D8'
        CertificateStoreName  = 'WebHosting'
        SslFlags              = 1
    } -ClientOnly
    New-CimInstance -ClassName MSFT_xWebBindingInformation -Namespace root/microsoft/Windows/DesiredStateConfiguration -Property @{
        Protocol              = 'https'
        IPAddress             = '*'
        Port                  = 443
        HostName              = '*.migrationwiz.com'
        CertificateThumbprint = 'DE0A409C2F2BF8DF47C9154EDE3C3309CAB9E0F7'
        CertificateStoreName  = 'WebHosting'
        SslFlags              = 1
    } -ClientOnly
)

Update-WebsiteBinding -Name MigrationWiz -BindingInfo $BindingInfo

Despite different CertificateThumbprint specified for the first and second binding BOTH get the same (first) certificate assigned!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugThe issue is a bug.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions