<?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: PSM Upgrade fails with error Invalid domain, username or Password. in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm-upgrade-fails-with-error-invalid-domain-username-or-password/m-p/1404775#M5558</link>
    <description>&lt;P&gt;Is there a valid LDAPS cert present on the DC that is issued to the FQDN of the DC? and is that cert trusted by the PSM connector server?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/CM-Update-PSM-fails-with-error-Invalid-domain-username-or-Password - both those checks must succeed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This LDAPS check by the CM agent was added sometime last year so if previous upgrades were prior to that, they may have gone through without any issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Check point 4 in the 'Before You Begin' section here: https://docs.cyberark.com/ispss-deployment/latest/en/content/privilege%20cloud/privcloud-connectorinstall-cm.htm#Beforeyoubegin&lt;/P&gt;</description>
    <pubDate>Tue, 10 Feb 2026 05:44:21 GMT</pubDate>
    <dc:creator>Tanishq</dc:creator>
    <dc:date>2026-02-10T05:44:21Z</dc:date>
    <item>
      <title>PSM Upgrade fails with error Invalid domain, username or Password.</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm-upgrade-fails-with-error-invalid-domain-username-or-password/m-p/1404774#M5557</link>
      <description>&lt;P&gt;For PSM Upgrade encountering the Invalid domain, username or Password error, is it enough that only the root certificate and intermediate certificate was uploaded in the certificate store? the customer has raised a valid point regarding why the previous upgrade was successful with this specific certificate configuration.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Although the TNC (Test-NetConnection) to the LDAP server was successful, the LDP.exe bind failed.&amp;nbsp;What could be the other cause for the error?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Feb 2026 00:19:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm-upgrade-fails-with-error-invalid-domain-username-or-password/m-p/1404774#M5557</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-02-10T00:19:42Z</dc:date>
    </item>
    <item>
      <title>Re: PSM Upgrade fails with error Invalid domain, username or Password.</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm-upgrade-fails-with-error-invalid-domain-username-or-password/m-p/1404775#M5558</link>
      <description>&lt;P&gt;Is there a valid LDAPS cert present on the DC that is issued to the FQDN of the DC? and is that cert trusted by the PSM connector server?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/CM-Update-PSM-fails-with-error-Invalid-domain-username-or-Password - both those checks must succeed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This LDAPS check by the CM agent was added sometime last year so if previous upgrades were prior to that, they may have gone through without any issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Check point 4 in the 'Before You Begin' section here: https://docs.cyberark.com/ispss-deployment/latest/en/content/privilege%20cloud/privcloud-connectorinstall-cm.htm#Beforeyoubegin&lt;/P&gt;</description>
      <pubDate>Tue, 10 Feb 2026 05:44:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm-upgrade-fails-with-error-invalid-domain-username-or-password/m-p/1404775#M5558</guid>
      <dc:creator>Tanishq</dc:creator>
      <dc:date>2026-02-10T05:44:21Z</dc:date>
    </item>
  </channel>
</rss>

