<?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: IP address used for Common Name in SSL Forward Proxy Cert in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ip-address-used-for-common-name-in-ssl-forward-proxy-cert/m-p/22043#M16095</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Miller,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You can use any common name or IP address. Assume this common name as say verisign or Godaddy. For example, you gave a common name as "My Company" and user went to &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://google.com" rel="nofollow"&gt;https://google.com&lt;/A&gt;&lt;SPAN&gt;, when a user looks at certificate, it will look like My Company has signed Google.com.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We just have to make sure that this cert is installed on Trusted Root Cert on client's machine. Unlike captive portal or Global Protect, common name is not of that importance. Hope this helps. Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Oct 2014 15:32:40 GMT</pubDate>
    <dc:creator>ssharma</dc:creator>
    <dc:date>2014-10-07T15:32:40Z</dc:date>
    <item>
      <title>IP address used for Common Name in SSL Forward Proxy Cert</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ip-address-used-for-common-name-in-ssl-forward-proxy-cert/m-p/22042#M16094</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm getting ready to generate a CSR for an SSL Forward Proxy Cert and I wanted to know which IP address should I use for the Common Name.&amp;nbsp; I would like to inspect SSL traffic that is sourced from both my Trusted zone as well as my DMZ zone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Should I use the IP address associated with my Trusted zone?&lt;/P&gt;&lt;P&gt;2) If I use the IP address of my Trusted zone interface, will that cause hosts within my DMZ zone to throw an error with the certificate?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Oct 2014 14:45:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ip-address-used-for-common-name-in-ssl-forward-proxy-cert/m-p/22042#M16094</guid>
      <dc:creator>ma.miller</dc:creator>
      <dc:date>2014-10-07T14:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: IP address used for Common Name in SSL Forward Proxy Cert</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ip-address-used-for-common-name-in-ssl-forward-proxy-cert/m-p/22043#M16095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Miller,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You can use any common name or IP address. Assume this common name as say verisign or Godaddy. For example, you gave a common name as "My Company" and user went to &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://google.com" rel="nofollow"&gt;https://google.com&lt;/A&gt;&lt;SPAN&gt;, when a user looks at certificate, it will look like My Company has signed Google.com.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We just have to make sure that this cert is installed on Trusted Root Cert on client's machine. Unlike captive portal or Global Protect, common name is not of that importance. Hope this helps. Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Oct 2014 15:32:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ip-address-used-for-common-name-in-ssl-forward-proxy-cert/m-p/22043#M16095</guid>
      <dc:creator>ssharma</dc:creator>
      <dc:date>2014-10-07T15:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: IP address used for Common Name in SSL Forward Proxy Cert</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ip-address-used-for-common-name-in-ssl-forward-proxy-cert/m-p/22044#M16096</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/u1/25764"&gt;ma.miller&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Welcome to forums.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use any common name for the certificate just the requirement is that the CA that issued the certificate must be in the Trusted Cert Store.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is need to install the certificate itself, just the CA which assigned that certificate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the certificate was self signed then you need to import the certificate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Oct 2014 15:52:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ip-address-used-for-common-name-in-ssl-forward-proxy-cert/m-p/22044#M16096</guid>
      <dc:creator>bat</dc:creator>
      <dc:date>2014-10-07T15:52:46Z</dc:date>
    </item>
  </channel>
</rss>

