<?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>question Re: Ambari Https (Broken HTTPS) in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143127#M40139</link>
    <description>&lt;P&gt;@mkataria&lt;/P&gt;&lt;P&gt;Is it self signed cert? did you try adding the host into trusted sites in the browser?&lt;/P&gt;&lt;P&gt;You can cross check the cert creation process with below article,&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/50405/how-to-enable-https-for-apache-ambari-using-jks.html" target="_blank"&gt;https://community.hortonworks.com/articles/50405/how-to-enable-https-for-apache-ambari-using-jks.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Sep 2016 01:26:29 GMT</pubDate>
    <dc:creator>apappu</dc:creator>
    <dc:date>2016-09-09T01:26:29Z</dc:date>
    <item>
      <title>Ambari Https (Broken HTTPS)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143126#M40138</link>
      <description>&lt;P&gt;While securing Ambari Sever for Https, we can successfully login to https and default port 8443, however the https  is stoked out and says &lt;STRONG&gt;This page is insecure (broken HTTPS).&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;We are using wildcard certs initially in .cer format however have to convert it to .pem format using openssl.&lt;/P&gt;&lt;P&gt;What is the preferred format and encryption for the Certs.&lt;/P&gt;&lt;P&gt;The current error says&lt;/P&gt;&lt;P&gt;1) SHA-1 Certificate
The certificate for this site expires in 2017 or later, and the certificate chain contains a certificate signed using SHA-1.&lt;/P&gt;&lt;P&gt;2) Certificate Error
There are issues with the site's certificate chain (net::ERR_CERT_COMMON_NAME_INVALID).&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mayank&lt;/P&gt;</description>
      <pubDate>Fri, 09 Sep 2016 01:08:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143126#M40138</guid>
      <dc:creator>mkataria</dc:creator>
      <dc:date>2016-09-09T01:08:55Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari Https (Broken HTTPS)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143127#M40139</link>
      <description>&lt;P&gt;@mkataria&lt;/P&gt;&lt;P&gt;Is it self signed cert? did you try adding the host into trusted sites in the browser?&lt;/P&gt;&lt;P&gt;You can cross check the cert creation process with below article,&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/50405/how-to-enable-https-for-apache-ambari-using-jks.html" target="_blank"&gt;https://community.hortonworks.com/articles/50405/how-to-enable-https-for-apache-ambari-using-jks.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Sep 2016 01:26:29 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143127#M40139</guid>
      <dc:creator>apappu</dc:creator>
      <dc:date>2016-09-09T01:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari Https (Broken HTTPS)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143128#M40140</link>
      <description>&lt;P&gt;We are using a single wildcard cert provided by enterprise CA.&lt;/P&gt;&lt;P&gt;Thanks
Mayank&lt;/P&gt;</description>
      <pubDate>Fri, 09 Sep 2016 01:29:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143128#M40140</guid>
      <dc:creator>mkataria</dc:creator>
      <dc:date>2016-09-09T01:29:12Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari Https (Broken HTTPS)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143129#M40141</link>
      <description>&lt;P&gt;Works for IE, however still broken for Chrome.&lt;/P&gt;&lt;P&gt;Any advices/help is appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Sep 2016 22:21:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143129#M40141</guid>
      <dc:creator>mkataria</dc:creator>
      <dc:date>2016-09-23T22:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari Https (Broken HTTPS)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143130#M40142</link>
      <description>&lt;P&gt;Figured it out, I generated a new cert and used &lt;STRONG&gt;Signature Algorithm as sha256RSA&lt;/STRONG&gt;  (s&lt;STRONG&gt;ignature hash algorithm as sha256)&lt;/STRONG&gt; however the ones I had earlier were SHA1RSA and SHA1 respectively. &lt;/P&gt;&lt;P&gt;Seems like ShA1 is week but IE doesn't seem to care, Chrome was not happy about it.&lt;/P&gt;&lt;P&gt;If it's a internal ONLY cluster and you are using a local CA authority (internal or self sign) you can still live with Sha1.&lt;/P&gt;&lt;P&gt;You will still achieve Secure TLS connection and Secure Resources however with a  warning &lt;STRONG&gt;This page is insecure (broken HTTPS).&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Hope this helps and thanks community to think.&lt;/P&gt;&lt;P&gt;Regards
Mayank&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2016 21:09:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143130#M40142</guid>
      <dc:creator>mkataria</dc:creator>
      <dc:date>2016-09-29T21:09:44Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari Https (Broken HTTPS)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143131#M40143</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/395/mkataria.html" nodeid="395"&gt;@mkataria&lt;/A&gt; Did you get solution ,can you share steps performed with wild card cert.&lt;/P&gt;</description>
      <pubDate>Sat, 13 Oct 2018 18:37:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-Https-Broken-HTTPS/m-p/143131#M40143</guid>
      <dc:creator>rajat_dua09</dc:creator>
      <dc:date>2018-10-13T18:37:14Z</dc:date>
    </item>
  </channel>
</rss>

