remoting https listener with a wildcard certificate

Welcome Forums General PowerShell Q&A remoting https listener with a wildcard certificate

This topic contains 3 replies, has 3 voices, and was last updated by

4 years, 4 months ago.

  • Author
  • #19813

    Points: 1
    Rank: Member

    I have a wilcard certificate such as *, I have a server with a dns url of, this configuration fails the CN check, my testing shows that the cert has to be * I don't see a way around this without skipping the check, so will just have to change my cert, just means I need more certificates, rather than just one.

  • #19815

    Points: 1,811
    Helping HandTeam Member
    Rank: Community Hero

    Correct. Wildcard certificates only cover a single wildcard (e.g., * not multiple (*.*

  • #19822

    Points: 0
    Rank: Member

    You should still be able to accomplish this with a single certificate, though. You just may need multiple Subject Alternative Name values on the cert. I've read conflicting reports as to whether a DNS name of *.* on a certificate will work with modern browsers or not; you'd have to test it to see if it's that easy. If not, then you may need to have multiple SANs for each domain (*, * , etc.)

  • #19846

    Points: 1
    Rank: Member

    Didn't realise you could have SANs in a wildcard cert, I'll give that a try. If it works I'll update here.

The topic ‘remoting https listener with a wildcard certificate’ is closed to new replies.

denizli escort samsun escort muğla escort ataşehir escort kuşadası escort