<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Certificates on Boldly Going Nowhere</title>
    <link>https://martynrees.github.io/tags/certificates/</link>
    <description>Recent content in Certificates on Boldly Going Nowhere</description>
    <image>
      <title>Boldly Going Nowhere</title>
      <url>https://martynrees.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://martynrees.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.140.2</generator>
    <language>en</language>
    <lastBuildDate>Tue, 18 Feb 2020 09:38:21 +1030</lastBuildDate>
    <atom:link href="https://martynrees.github.io/tags/certificates/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CUCM Convert LDAP to LDAPS</title>
      <link>https://martynrees.github.io/post/cucm-ldaps/</link>
      <pubDate>Tue, 18 Feb 2020 09:38:21 +1030</pubDate>
      <guid>https://martynrees.github.io/post/cucm-ldaps/</guid>
      <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;This post is applicable for both CUCM and Unity Connection, but for simplicity sake we will just cover CUCM here. The process of uploading and converting Unity Connection is the same. This process is also the same no matter which version of CUCM/Unity connection.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Cisco have released the following field notice that covers upcoming changes to connections between CUCM/unityCx and LDAP servers for syncronising and authenticating users.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/fieldNotice/cucm_b_fn-secure-ldap-mandatory-ad.html&#34;&gt;https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/fieldNotice/cucm_b_fn-secure-ldap-mandatory-ad.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The short of it is that Microsoft are enforcing that connections should now be over SSL rather than unencrypted transport methods. This was initially going to be enforced from March security patches onwards, but has now been pushed back. Regardless of the time frame though, it is important to make these changes now, rather than be caught in a rush later.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Google Chrome Revoked Self Signed Certificates</title>
      <link>https://martynrees.github.io/post/chrome-cert/</link>
      <pubDate>Fri, 03 Jan 2020 10:25:14 +1030</pubDate>
      <guid>https://martynrees.github.io/post/chrome-cert/</guid>
      <description>&lt;p&gt;Google Chrome can block you from getting to your lab devices (like your WLC) or other devices that have self signed certicates.
If you get an error like this, and you can&amp;rsquo;t get past, then there is still a way without having to buy a signed cert!&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;Certificate&#34; loading=&#34;lazy&#34; src=&#34;https://martynrees.github.io/img/cert-error.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;To get around this click somewhere on the page and then type &lt;strong&gt;thisisunsafe&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Then like magic Chrome will load the page!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
