<?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: Self Serve - Distrusted Certificate in Get Support</title>
    <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203392#M174314</link>
    <description>&lt;P&gt;The same thing happened to me the first time I loaded PM on my laptop to log in.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I honestly just went ahead and clicked on the “advance anyway” option and now it’s a perfectly secure website. I don’t quite understand why it had done that but once I proceeded, even before logging in, it became secure.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 07 Dec 2017 15:51:13 GMT</pubDate>
    <dc:creator>Clefort88</dc:creator>
    <dc:date>2017-12-07T15:51:13Z</dc:date>
    <item>
      <title>Self Serve - Distrusted Certificate</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203181#M174306</link>
      <description>&lt;P&gt;When accessing the self serve site "&lt;A href="https://selfserve.publicmobile.ca/" target="_blank"&gt;https://selfserve.publicmobile.ca/&lt;/A&gt;" within the chrome browser (Version 62) the following alert appears in the console:&lt;BR /&gt;&lt;BR /&gt;The certificate used to load &lt;A href="https://selfserve.publicmobile.ca/" target="_blank"&gt;https://selfserve.publicmobile.ca/&lt;/A&gt; uses an SSL certificate that will be distrusted in an upcoming release of Chrome. Once distrusted, users will be prevented from loading this resource. See &lt;A href="https://g.co/chrome/symantecpkicerts" target="_blank"&gt;https://g.co/chrome/symantecpkicerts&lt;/A&gt; for more information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It probably won't be an issue given the current cert expires April 13, 2018 and Chrome Version 66 won't be stable until ~&lt;SPAN&gt;April 17, 2018 but I figured it should be brought to everyone's attention.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jan 2022 08:41:30 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203181#M174306</guid>
      <dc:creator>Martin_G</dc:creator>
      <dc:date>2022-01-05T08:41:30Z</dc:date>
    </item>
    <item>
      <title>Re: Self Serve - Distrusted Certificate</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203203#M174308</link>
      <description>&lt;P&gt;SSL certificate problems have been around for a long time. &amp;nbsp;It's one of those design features of the self serve system that needs attention. &amp;nbsp;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/3757"&gt;@Luddite&lt;/a&gt;, here's another item for your comprehensive list of gremlins.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 18:35:31 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203203#M174308</guid>
      <dc:creator>will13am</dc:creator>
      <dc:date>2017-12-06T18:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: Self Serve - Distrusted Certificate</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203249#M174310</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/16361"&gt;@will13am&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;SSL certificate problems have been around for a long time. &amp;nbsp;It's one of those design features of the self serve system that needs attention. &amp;nbsp;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/3757"&gt;@Luddite&lt;/a&gt;, here's another item for your comprehensive list of gremlins.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/16361"&gt;@will13am&lt;/a&gt;&amp;nbsp;What is the workaround for this error?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 20:59:08 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203249#M174310</guid>
      <dc:creator>Luddite</dc:creator>
      <dc:date>2017-12-06T20:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: Self Serve - Distrusted Certificate</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203301#M174312</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/3757"&gt;@Luddite&lt;/a&gt; wrote:&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/16361"&gt;@will13am&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;SSL certificate problems have been around for a long time. &amp;nbsp;It's one of those design features of the self serve system that needs attention. &amp;nbsp;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/3757"&gt;@Luddite&lt;/a&gt;, here's another item for your comprehensive list of gremlins.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/16361"&gt;@will13am&lt;/a&gt;&amp;nbsp;What is the workaround for this error?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I use Dolphin browser. &amp;nbsp;That says a lot about this browser, lol.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2017 01:45:12 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203301#M174312</guid>
      <dc:creator>will13am</dc:creator>
      <dc:date>2017-12-07T01:45:12Z</dc:date>
    </item>
    <item>
      <title>Re: Self Serve - Distrusted Certificate</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203392#M174314</link>
      <description>&lt;P&gt;The same thing happened to me the first time I loaded PM on my laptop to log in.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I honestly just went ahead and clicked on the “advance anyway” option and now it’s a perfectly secure website. I don’t quite understand why it had done that but once I proceeded, even before logging in, it became secure.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2017 15:51:13 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203392#M174314</guid>
      <dc:creator>Clefort88</dc:creator>
      <dc:date>2017-12-07T15:51:13Z</dc:date>
    </item>
    <item>
      <title>Re: Self Serve - Distrusted Certificate</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203468#M174316</link>
      <description>&lt;P&gt;On chrome you can hit advance and force it to go to unsecure page.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2017 20:12:19 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/Self-Serve-Distrusted-Certificate/m-p/203468#M174316</guid>
      <dc:creator>sirvar</dc:creator>
      <dc:date>2017-12-07T20:12:19Z</dc:date>
    </item>
  </channel>
</rss>

