<?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 Cisco ISE Licensing - Failed to verify signature in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-licensing-failed-to-verify-signature/m-p/5134468#M590207</link>
    <description>&lt;P&gt;Hello ISE guys,&lt;/P&gt;&lt;P&gt;we are running ISE 3.2 deployment and a few days ago we had to reboot both our PAN Nodes. Reboot Secondary (B Node), wait, promote to primary (A-&amp;gt;B), wait, reboot secondary (A Node). Since then we are facing CSSM licensing problems -&amp;gt; "Satellite Authorization Renewal: Details=Failed to verify signature". Now the primary PAN Node disappered from the On-Prem CSSM Satellite and the Secondary got registered. Unfortunaltely now the authorization is failing the the ISE deployment cannot sync with the CSSM Satellite.&lt;/P&gt;&lt;P&gt;I tried Refresh and Renew Registration but the issue persist since the token/SN cannot be verified.&lt;/P&gt;&lt;P&gt;Does anyone has experience with the mentioned issue or is there a certain procedure that we need to stick to?&lt;/P&gt;&lt;P&gt;Thank you in advance!&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jun 2024 08:59:42 GMT</pubDate>
    <dc:creator>klnnnnng</dc:creator>
    <dc:date>2024-06-21T08:59:42Z</dc:date>
    <item>
      <title>Cisco ISE Licensing - Failed to verify signature</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-licensing-failed-to-verify-signature/m-p/5134468#M590207</link>
      <description>&lt;P&gt;Hello ISE guys,&lt;/P&gt;&lt;P&gt;we are running ISE 3.2 deployment and a few days ago we had to reboot both our PAN Nodes. Reboot Secondary (B Node), wait, promote to primary (A-&amp;gt;B), wait, reboot secondary (A Node). Since then we are facing CSSM licensing problems -&amp;gt; "Satellite Authorization Renewal: Details=Failed to verify signature". Now the primary PAN Node disappered from the On-Prem CSSM Satellite and the Secondary got registered. Unfortunaltely now the authorization is failing the the ISE deployment cannot sync with the CSSM Satellite.&lt;/P&gt;&lt;P&gt;I tried Refresh and Renew Registration but the issue persist since the token/SN cannot be verified.&lt;/P&gt;&lt;P&gt;Does anyone has experience with the mentioned issue or is there a certain procedure that we need to stick to?&lt;/P&gt;&lt;P&gt;Thank you in advance!&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 08:59:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-licensing-failed-to-verify-signature/m-p/5134468#M590207</guid>
      <dc:creator>klnnnnng</dc:creator>
      <dc:date>2024-06-21T08:59:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Licensing - Failed to verify signature</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-licensing-failed-to-verify-signature/m-p/5134736#M590216</link>
      <description>&lt;P&gt;ISE and on-prem CSSM licensing has always been unreliable in my experience and not sure who is causing this (ISE, or CSSM). If you find a stable combination of the two, then consider yourself lucky.&amp;nbsp; I occasionally have to de-register and re-register nodes to CSSM because all attempts to sync and refresh etc. don't work. Don't waste your time trying. Just de-register from CSSM, log into CSSM and if the ISE node is still there, manually delete it. Then generate a token and re-register. The CSSM feels like it's built on some pretty simplistic opensource code and I would hazard a guess, that it's not implemented in the most robust ways.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 22:02:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-licensing-failed-to-verify-signature/m-p/5134736#M590216</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-06-21T22:02:49Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Licensing - Failed to verify signature</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-licensing-failed-to-verify-signature/m-p/5134814#M590221</link>
      <description>&lt;P&gt;Hello Arne,&lt;/P&gt;&lt;P&gt;after all the unsuccessful Refresh and Renew registration attempts this is what we did and it helped. I thought there should or could be a more elegant solution to the problem. Thank you for the thorough explanation and sharing your expertise.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 22 Jun 2024 08:03:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-licensing-failed-to-verify-signature/m-p/5134814#M590221</guid>
      <dc:creator>klnnnnng</dc:creator>
      <dc:date>2024-06-22T08:03:38Z</dc:date>
    </item>
  </channel>
</rss>

