<?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: ExclusiveAccess automatic check in not working after version upgrade in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407687#M84034</link>
    <description>&lt;P&gt;Yes, &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The PSMs still communicate with the PVWAs in port 443&lt;/P&gt;</description>
    <pubDate>Wed, 25 Mar 2026 17:39:26 GMT</pubDate>
    <dc:creator>LGoncalves</dc:creator>
    <dc:date>2026-03-25T17:39:26Z</dc:date>
    <item>
      <title>ExclusiveAccess automatic check in not working after version upgrade</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407683#M84030</link>
      <description>&lt;P&gt;After upgrading PAM self-hosted environment (Vault, PVWAs, PSMs, CPMs) to version 15.0 (from 14.0), the automatic checkin for "ExclusiveAccess" platforms are not working anymore. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the accounts, I see the error:&lt;/P&gt;&lt;P&gt;PSMDisconnect error:&lt;/P&gt;&lt;P&gt;PSMSR1258E REST call failed&lt;/P&gt;&lt;P&gt;reason: CAJWT001E Invalid JWT token.&lt;/P&gt;&lt;P&gt;PSMApp&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone knows how to solve this issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2026 16:36:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407683#M84030</guid>
      <dc:creator>LGoncalves</dc:creator>
      <dc:date>2026-03-24T16:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: ExclusiveAccess automatic check in not working after version upgrade</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407684#M84031</link>
      <description>&lt;P&gt;Basically, it is indicating that PVWA API is not communicating properly from PSM Servers. Have you defined PVWA API url in vault.ini of PSM Servers? If not, please do. &lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2026 20:17:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407684#M84031</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2026-03-24T20:17:59Z</dc:date>
    </item>
    <item>
      <title>Re: ExclusiveAccess automatic check in not working after version upgrade</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407685#M84032</link>
      <description>&lt;P&gt;Yes, they are like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Addresses="https://&amp;lt;pvwa_url&amp;gt;/passwordvault/api"&lt;/P&gt;&lt;P&gt;ApiKeyPath="D:\CyberArk\PSM\Vault\apigw.cred"&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2026 13:36:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407685#M84032</guid>
      <dc:creator>LGoncalves</dc:creator>
      <dc:date>2026-03-25T13:36:23Z</dc:date>
    </item>
    <item>
      <title>Re: ExclusiveAccess automatic check in not working after version upgrade</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407686#M84033</link>
      <description>&lt;P&gt;Have you tested if PVWA url is communicating on 443 from PSM servers securely?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2026 14:11:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407686#M84033</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2026-03-25T14:11:49Z</dc:date>
    </item>
    <item>
      <title>Re: ExclusiveAccess automatic check in not working after version upgrade</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407687#M84034</link>
      <description>&lt;P&gt;Yes, &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The PSMs still communicate with the PVWAs in port 443&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2026 17:39:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407687#M84034</guid>
      <dc:creator>LGoncalves</dc:creator>
      <dc:date>2026-03-25T17:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: ExclusiveAccess automatic check in not working after version upgrade</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407688#M84035</link>
      <description>&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/ExclusiveUnlockAfterPSMSession-unlocks-checks-account-in-but-gives-error" href="https://community.cyberark.com/s/article/ExclusiveUnlockAfterPSMSession-unlocks-checks-account-in-but-gives-error" target="_blank"&gt;ExclusiveUnlockAfterPSMSession unlocks/checks account in, but gives error PSMSR1258E REST call failed. reason: PASWS039E Account [xxx_x] was not found. (Codes: -1, -1)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/How-do-you-re-sync-the-api-cred-file-for-the-CPM-Scanner-service-from-v10-7" href="https://community.cyberark.com/s/article/How-do-you-re-sync-the-api-cred-file-for-the-CPM-Scanner-service-from-v10-7" target="_blank"&gt;CPM scanner - How do I resync the API&amp;nbsp;credfile for the CPM Scanner service?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/Accounts-Automatic-Unlock" href="https://community.cyberark.com/s/article/Accounts-Automatic-Unlock" target="_blank"&gt;Accounts Automatic Unlock not working&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/When-using-ApiKeyManager-it-fails-with-ERROR-001E-Failed-to-perform-request-Reason-SSL-connect-error" href="https://community.cyberark.com/s/article/When-using-ApiKeyManager-it-fails-with-ERROR-001E-Failed-to-perform-request-Reason-SSL-connect-error" target="_blank"&gt;CPM-When using ApiKeyManager it fails with "[ERROR] 001E Failed to perform request (Reason=[SSL connect error])"&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/PASWS001E-Error-occurred-CAJWT002E-JWT-token-structure-is-invalid-missing-or-wrong-fields-in-token" href="https://community.cyberark.com/s/article/PASWS001E-Error-occurred-CAJWT002E-JWT-token-structure-is-invalid-missing-or-wrong-fields-in-token" target="_blank"&gt;PASWS001E Error occurred: CAJWT002E JWT token structure is invalid - missing or wrong fields in token.&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2026 17:49:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/exclusiveaccess-automatic-check-in-not-working-after-version/m-p/1407688#M84035</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2026-03-25T17:49:52Z</dc:date>
    </item>
  </channel>
</rss>

