<?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 Intermediate SSL Certificate in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/intermediate-ssl-certificate/m-p/1918324#M37018</link>
    <description>&lt;P&gt;&lt;SPAN style="font-family: tahoma,arial,helvetica,sans-serif;"&gt;Hi Guys,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: tahoma,arial,helvetica,sans-serif;"&gt;Can anyone please explain what is an intermediate SSL certificate and if it has got anything do with the configuration of Chaningroup in ACE&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: tahoma,arial,helvetica,sans-serif;"&gt;What is the use of an intermediate SSL certificate ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: tahoma,arial,helvetica,sans-serif;"&gt;CF&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 08 Apr 2012 13:27:29 GMT</pubDate>
    <dc:creator>Cisco Freak</dc:creator>
    <dc:date>2012-04-08T13:27:29Z</dc:date>
    <item>
      <title>Intermediate SSL Certificate</title>
      <link>https://community.cisco.com/t5/application-networking/intermediate-ssl-certificate/m-p/1918324#M37018</link>
      <description>&lt;P&gt;&lt;SPAN style="font-family: tahoma,arial,helvetica,sans-serif;"&gt;Hi Guys,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: tahoma,arial,helvetica,sans-serif;"&gt;Can anyone please explain what is an intermediate SSL certificate and if it has got anything do with the configuration of Chaningroup in ACE&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: tahoma,arial,helvetica,sans-serif;"&gt;What is the use of an intermediate SSL certificate ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: tahoma,arial,helvetica,sans-serif;"&gt;CF&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 08 Apr 2012 13:27:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/intermediate-ssl-certificate/m-p/1918324#M37018</guid>
      <dc:creator>Cisco Freak</dc:creator>
      <dc:date>2012-04-08T13:27:29Z</dc:date>
    </item>
    <item>
      <title>Intermediate SSL Certificate</title>
      <link>https://community.cisco.com/t5/application-networking/intermediate-ssl-certificate/m-p/1918325#M37019</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi CF,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;End entity certificates chained to an intermediate certificate&amp;nbsp; represent the highest possible security solution for Certification&amp;nbsp; Authorities and therefore their customers.&amp;nbsp; There exists a very small&amp;nbsp; possibility, consistent amongst all certification authorities, that the&amp;nbsp; certificate used to sign end entity certificates could be compromised.&amp;nbsp; The signing process itself mandates that the signing certificate must be&amp;nbsp; accessible in order to perform the signing operation.&amp;nbsp; In the case of&amp;nbsp; an intermediate certificate, the corresponding root certificate is&amp;nbsp; secured/locked away, eliminating the possibility of it being compromised&amp;nbsp; by daily signing processes.&amp;nbsp; End entity certificates directly signed by&amp;nbsp; root certificates (i.e. no intermediate protection) provide no recourse&amp;nbsp; should the root certificate itself become compromised. If an&amp;nbsp; Intermediate were to be compromised then new intermediates could be&amp;nbsp; created and new end entity certificates could be issued. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once a&amp;nbsp; root itself is compromised there is no solution or replacement strategy.&amp;nbsp;&amp;nbsp; It is therefore considered industry best practice to use intermediate&amp;nbsp; certificates. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Courtesy : WhichSSL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now coming to ACE , we need to configure the certificate chain group , to allocate all the root certificates , if we miss one of the root certificate in the chain group , end user will be getting the certificate warning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it is complusory we shold configure the chaingroup will all the root certificate assosicated with the Intermediate certificate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PMD&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 08 Apr 2012 14:35:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/intermediate-ssl-certificate/m-p/1918325#M37019</guid>
      <dc:creator>parveesm123</dc:creator>
      <dc:date>2012-04-08T14:35:05Z</dc:date>
    </item>
    <item>
      <title>Re: Intermediate SSL Certificate</title>
      <link>https://community.cisco.com/t5/application-networking/intermediate-ssl-certificate/m-p/4009250#M51168</link>
      <description>&lt;P&gt;Basically, there is a chain of certificates is required for a browser to show the secured domain. This could run to many lines if we had to make you understand here. Read this detailed and easy explanation of &lt;A href="https://www.https.in/blog/ssl-certificate-chain/" target="_blank" rel="noopener"&gt;SSL certificate chain&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2020 06:43:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/intermediate-ssl-certificate/m-p/4009250#M51168</guid>
      <dc:creator>httpsIndia50866</dc:creator>
      <dc:date>2020-01-10T06:43:38Z</dc:date>
    </item>
  </channel>
</rss>

