<?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: Jabber 14 getting invalid and expired cert warning CUPS 12.5 in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4711483#M48358</link>
    <description>&lt;P&gt;Yes, restarted all services several times. Same results.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 27 Oct 2022 05:06:07 GMT</pubDate>
    <dc:creator>iverson.justin</dc:creator>
    <dc:date>2022-10-27T05:06:07Z</dc:date>
    <item>
      <title>Jabber 14 getting invalid and expired cert warning CUPS 12.5</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4711416#M48355</link>
      <description>&lt;P&gt;Getting invalid and expired cert warnings for CUPS servers. PUB shows expired and SUB shows invalid.&amp;nbsp; CUP-XMPP &amp;amp; Tomcat have valid enterprise certs, nodes have been both completely restarted. My SUB is new and CUPS sub is still offering the self-signed cert, my PUB is still offering the expired cert from 30 days go. Deleted and uploaded certs plus restarted cluster, still getting errors on Jabber.&amp;nbsp; TAC is looking but taking bit.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2022 03:14:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4711416#M48355</guid>
      <dc:creator>iverson.justin</dc:creator>
      <dc:date>2022-10-27T03:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber 14 getting invalid and expired cert warning CUPS 12.5</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4711468#M48356</link>
      <description>&lt;P&gt;Thump Rule renew expired certificates and restart the related services.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have you done this ?&lt;/P&gt;
&lt;DIV id="sconnect-is-installed" style="display: none;"&gt;2.12.0.0&lt;/DIV&gt;</description>
      <pubDate>Thu, 27 Oct 2022 04:27:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4711468#M48356</guid>
      <dc:creator>Nithin Eluvathingal</dc:creator>
      <dc:date>2022-10-27T04:27:14Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber 14 getting invalid and expired cert warning CUPS 12.5</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4711483#M48358</link>
      <description>&lt;P&gt;Yes, restarted all services several times. Same results.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2022 05:06:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4711483#M48358</guid>
      <dc:creator>iverson.justin</dc:creator>
      <dc:date>2022-10-27T05:06:07Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber 14 getting invalid and expired cert warning CUPS 12.5</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4711490#M48359</link>
      <description>&lt;P&gt;Can you please share screenshots from your servers from the certificate management page?&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2022 05:36:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4711490#M48359</guid>
      <dc:creator>Roger Kallberg</dc:creator>
      <dc:date>2022-10-27T05:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber 14 getting invalid and expired cert warning CUPS 12.5</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4714565#M48368</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="iversonjustin_0-1667363489595.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/166919i517A3F96E1A38F2F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="iversonjustin_0-1667363489595.png" alt="iversonjustin_0-1667363489595.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Screen shot of cup-xmpp cert, Jabber client is still presenting the self signed IMP cert even though I replaced cup-xmpp with enterprise CA-signed cert.&amp;nbsp; Getting no where with TAC, they say its bug&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb89326" target="_blank" rel="noopener"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb89326&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Jabber client cert is pulling:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="iversonjustin_1-1667363737415.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/166920i74B9CE63242FC3C5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="iversonjustin_1-1667363737415.png" alt="iversonjustin_1-1667363737415.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2022 04:35:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4714565#M48368</guid>
      <dc:creator>iverson.justin</dc:creator>
      <dc:date>2022-11-02T04:35:47Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber 14 getting invalid and expired cert warning CUPS 12.5</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4714593#M48370</link>
      <description>&lt;P&gt;Really hard to see anything on the certificate screenshot, will check again from a computer when I get to work. On the bug, if you’re truly hitting that defect TAC should be able to help you with removal of the stuck certificate(s) from their root access.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2022 06:00:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4714593#M48370</guid>
      <dc:creator>Roger Kallberg</dc:creator>
      <dc:date>2022-11-02T06:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber 14 getting invalid and expired cert warning CUPS 12.5</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4714624#M48371</link>
      <description>&lt;P&gt;Have you restarted the services and server after uploading the CA signed certificates ?&lt;/P&gt;
&lt;P&gt;If you are hit with the BUG TAC could be able to Fix it .&lt;/P&gt;
&lt;DIV id="sconnect-is-installed" style="display: none;"&gt;2.12.0.0&lt;/DIV&gt;</description>
      <pubDate>Wed, 02 Nov 2022 06:08:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4714624#M48371</guid>
      <dc:creator>Nithin Eluvathingal</dc:creator>
      <dc:date>2022-11-02T06:08:27Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber 14 getting invalid and expired cert warning CUPS 12.5</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4736635#M48535</link>
      <description>&lt;P&gt;TAC resolved with root access and had to remove bad cert twice. BUG&amp;nbsp;CSCwa01599&lt;/P&gt;
&lt;P&gt;&lt;U&gt;Problem Description&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;Presence 14.0.1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Publisher node seemed to have a known defect (CSCwa01599) but the workaround was applied without success.&amp;nbsp; The old expired certificate was still being presented.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;U&gt;Summary&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;We thoroughly checked all locations for the certificate including database and file system.&amp;nbsp; We confirmed that the new certificate was present for all locations mentioned.&amp;nbsp; however, the problem was a backup copy of the xmpp.pem file located in the same directory of /usr/local/xcp/certs/xmpp/. &amp;nbsp;This backup file was being presented to jabber even though it was named xmpp.pem_orig, which was the old, expired certificate.&amp;nbsp; So simply deleting this file from the server followed by the same service restarts for Cisco XCP Connection Manager and Cisco XCP Router resolved the issue.&lt;/P&gt;</description>
      <pubDate>Sun, 11 Dec 2022 19:22:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-14-getting-invalid-and-expired-cert-warning-cups-12-5/m-p/4736635#M48535</guid>
      <dc:creator>iverson.justin</dc:creator>
      <dc:date>2022-12-11T19:22:42Z</dc:date>
    </item>
  </channel>
</rss>

