<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cannot submit wildcard CNs to GlobalSign MSSL. in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/cannot-submit-wildcard-cns-to-globalsign-mssl/m-p/1419838#M567</link>
    <description>@sbirl I am creating a Venafi support ticket for you. It sounds like this is an error you should not be encountering so wed like to get to the bottom of it.</description>
    <pubDate>Fri, 23 Feb 2024 09:23:07 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-02-23T09:23:07Z</dc:date>
    <item>
      <title>Cannot submit wildcard CNs to GlobalSign MSSL.</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/cannot-submit-wildcard-cns-to-globalsign-mssl/m-p/1419837#M566</link>
      <description>End-user recently notified that his request for a wildcard CN was rejected.Failed to request certificate from GLOBALSIGNMSSL certification authority. External service responded with client error: 'Invalid parameter combination. Please that check the parameters match the API specification.' Error: 11265But I know that Ive issued out a wildcard through the GlobalSign website in the past.So I tried, from the Venafi-side to re-create the request, and I received the same error. Had the user create a CSR and send it over to me, and I went into the GlobalSign site where I noticed two options:Double-checked the Certificate Authorities settings, and theres no option present about Single Domain -vs- Wildcard, so it looks like Single Domain wins by default.Any way to fix this? Itll make renewing this cert (and at least one other cert) impossible for the end-users..</description>
      <pubDate>Wed, 14 Feb 2024 21:25:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/cannot-submit-wildcard-cns-to-globalsign-mssl/m-p/1419837#M566</guid>
      <dc:creator>sbirl</dc:creator>
      <dc:date>2024-02-14T21:25:29Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot submit wildcard CNs to GlobalSign MSSL.</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/cannot-submit-wildcard-cns-to-globalsign-mssl/m-p/1419838#M567</link>
      <description>@sbirl I am creating a Venafi support ticket for you. It sounds like this is an error you should not be encountering so wed like to get to the bottom of it.</description>
      <pubDate>Fri, 23 Feb 2024 09:23:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/cannot-submit-wildcard-cns-to-globalsign-mssl/m-p/1419838#M567</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-23T09:23:07Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot submit wildcard CNs to GlobalSign MSSL.</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/cannot-submit-wildcard-cns-to-globalsign-mssl/m-p/1419839#M568</link>
      <description>@sbirl I am creating a Venafi support ticket for you. It sounds like this is an error you should not be encountering so wed like to get to the bottom of it.</description>
      <pubDate>Fri, 23 Feb 2024 09:23:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/cannot-submit-wildcard-cns-to-globalsign-mssl/m-p/1419839#M568</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-23T09:23:07Z</dc:date>
    </item>
  </channel>
</rss>

