<?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: Privilege Cloud URL is WRONG in Remote Access Sites. How can I change this URL so that it correctly reflects my organization's tenant? in Remote Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/privilege-cloud-url-is-wrong-in-remote-access-sites-how-can-i/m-p/1339922#M306</link>
    <description>&lt;P&gt;Hi @Tyler Sell​, if this is still an issue, I recommend that you open a Support ticket. &lt;/P&gt;</description>
    <pubDate>Fri, 02 Feb 2024 16:03:07 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-02-02T16:03:07Z</dc:date>
    <item>
      <title>Privilege Cloud URL is WRONG in Remote Access Sites. How can I change this URL so that it correctly reflects my organization's tenant?</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/privilege-cloud-url-is-wrong-in-remote-access-sites-how-can-i/m-p/1339921#M305</link>
      <description>&lt;P&gt;I have looked all over the menus and cannot find anywhere to change the site PVWA URL for my Privilege Cloud tenant within Remote Access. Because it is wrong, I get a DNS failure every time I try to connect to it. I did not set the name originally, so I am not sure where the Remote Access portal "got" the name that is has from. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The help page seems to imply that I can "set" the PVWA URL for this connector, and I would like to know how. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 01 Feb 2024 18:06:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/privilege-cloud-url-is-wrong-in-remote-access-sites-how-can-i/m-p/1339921#M305</guid>
      <dc:creator>TSell</dc:creator>
      <dc:date>2024-02-01T18:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: Privilege Cloud URL is WRONG in Remote Access Sites. How can I change this URL so that it correctly reflects my organization's tenant?</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/privilege-cloud-url-is-wrong-in-remote-access-sites-how-can-i/m-p/1339922#M306</link>
      <description>&lt;P&gt;Hi @Tyler Sell​, if this is still an issue, I recommend that you open a Support ticket. &lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2024 16:03:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/privilege-cloud-url-is-wrong-in-remote-access-sites-how-can-i/m-p/1339922#M306</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-02T16:03:07Z</dc:date>
    </item>
    <item>
      <title>Re: Privilege Cloud URL is WRONG in Remote Access Sites. How can I change this URL so that it correctly reflects my organization's tenant?</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/privilege-cloud-url-is-wrong-in-remote-access-sites-how-can-i/m-p/1339923#M307</link>
      <description>&lt;P&gt;I did that as well :). I just wanted to make sure that I wasn't missing any menus or actions that I could do &lt;I&gt;myself &lt;/I&gt;to resolve the issue without bothering the support engineers. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It does seem to be a genuine bug, though. The PVWA URL that we have in Privilege Cloud has not replicated out to other CyberArk Products. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2024 16:04:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/privilege-cloud-url-is-wrong-in-remote-access-sites-how-can-i/m-p/1339923#M307</guid>
      <dc:creator>TSell</dc:creator>
      <dc:date>2024-02-02T16:04:56Z</dc:date>
    </item>
  </channel>
</rss>

