<?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 Custom Domain Feature Implementation in Workforce Identity Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/custom-domain-feature-implementation/m-p/1393485#M1378</link>
    <description>&lt;P&gt;Our organization would like to implement the Custom domain feature to map our root tenant url to a subdomain of our public webpage. Management would like to know if implementing this feature require us to procure a new certificate from a commercia&lt;/P&gt;&lt;P&gt;l Certificate Authority or if could we use a certificate from our own internal CA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not familiar with how TLS is implemented on our public facing website so I'm not sure if we can get access to our private key as specified in the documentation. However is this what most people do in this situation?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help you could provide on this topic is much appreciated.&lt;/P&gt;</description>
    <pubDate>Tue, 11 Jan 2022 19:01:22 GMT</pubDate>
    <dc:creator>MC</dc:creator>
    <dc:date>2022-01-11T19:01:22Z</dc:date>
    <item>
      <title>Custom Domain Feature Implementation</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/custom-domain-feature-implementation/m-p/1393485#M1378</link>
      <description>&lt;P&gt;Our organization would like to implement the Custom domain feature to map our root tenant url to a subdomain of our public webpage. Management would like to know if implementing this feature require us to procure a new certificate from a commercia&lt;/P&gt;&lt;P&gt;l Certificate Authority or if could we use a certificate from our own internal CA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not familiar with how TLS is implemented on our public facing website so I'm not sure if we can get access to our private key as specified in the documentation. However is this what most people do in this situation?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help you could provide on this topic is much appreciated.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jan 2022 19:01:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/custom-domain-feature-implementation/m-p/1393485#M1378</guid>
      <dc:creator>MC</dc:creator>
      <dc:date>2022-01-11T19:01:22Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Domain Feature Implementation</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/custom-domain-feature-implementation/m-p/1393486#M1379</link>
      <description>&lt;P&gt;Haven't personally used that feature, but based on the documentation here (https://docs.cyberark.com/Product-Doc/OnlineHelp/Idaptive/Latest/en/Content/CoreServices/Authenticate/CustomDomain.htm), you need to provide your own certificate bundle (containing a private key and a server certificate) for that custom domain. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you want to host this under your publicly available domain (f.e. idaptive.company.net), you typically need to procure a certificate from a public CA (like DigiCert, Verisign, Lets-Encrypt, ...) and install that. Or if you already have a wildcard certificate (for *.company.net in this example), you need that certificate and its private key.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you are fine with the custom domain being only reachable via VPN or LAN (via idaptive.company-internal.private for example) then you can use a certificate signed by your internal CA, assuming all the clients accessing the Identity page already trust that CA.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jan 2022 08:43:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/custom-domain-feature-implementation/m-p/1393486#M1379</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-01-12T08:43:01Z</dc:date>
    </item>
  </channel>
</rss>

