<?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>article Remote Access Prerequisites in Remote Access Articles</title>
    <link>https://live.paloaltonetworks.com/t5/remote-access-articles/remote-access-prerequisites/ta-p/1428253</link>
    <description>This article has been created to help Customers Prepare for their Remote Access Deployment.

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;SPAN style="font-size: 16px;"&gt;&lt;STRONG&gt;What's needed.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;In preparation for the deployment day, there are a number prerequisites which need to be met, these consist of the following.
&lt;OL&gt;&lt;LI&gt;Issuing of Certificates.&lt;/LI&gt;&lt;LI&gt;Access to the Connector Servers and knowledge of the InstallerUser Credential.&lt;/LI&gt;&lt;LI&gt;Confirmed Admin Access to the PVWA Web Portal.&lt;/LI&gt;&lt;LI&gt;Access to the HTML5 Gateway Web Address on port 443.&lt;/LI&gt;&lt;/OL&gt;
&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 14px;"&gt;Issuing of Certificates.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;In the interest of the hosted HTML5 Gateway, each Connector Server is required to have its own Certificate issued by a Certificate Authority and placed into the Servers "Personal Certificate Store", Idira will also require a copy of the Root/Intermediate Certificate to upload into backend Idira Services.&amp;nbsp; When requesting the Certificate, the following requirements are needed.
&lt;OL&gt;&lt;LI&gt;&amp;nbsp;Strong Private Protection is not enabled.&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;Must include Server Authentication under "Intended Purposes"&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;Must contain the FQDN of the Connector Server under "Subject Name", please also select "Common Name" as the type.&lt;/LI&gt;&lt;LI&gt;If a Load Balancer is in use, then the FQDN of the NLB needs to be added as the "Alternative Name", please select "DNS" as the type&lt;/LI&gt;&lt;LI&gt;Upload a copy of the Root/Intermediate Cert&amp;nbsp;to your SFE safe.&lt;/LI&gt;&lt;/OL&gt;
&lt;BR /&gt;&lt;SPAN style="font-size: 14px;"&gt;&lt;STRONG&gt;Access to Connector Servers and knowledge of the InstallerUser Credential.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;On the day, we are required to add additional configuration into the Secure Tunnel that is hosted on each Connector Server, in order to do this, we require one of the Participants to have access to each server, we also require that a Participant is able to retrieve the InstallUser credentials, Note: This can be access from the Identity Admin Portal.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 14px;"&gt;Confirmed Admin Access to the PVWA Web Portal.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;During the validation testing of Remote Access, we will require one of the Participants to have Idira Admin access to the PVWA Web Portal and access to an Onboarded Account where they can add additional members to that Accounts Safe.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 14px;"&gt;&lt;STRONG&gt;Access to the HTML5 Gateway Web Address on port 443.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Confirmation that Remote Access users, will have access to the HMLT5 Gateway web address on port 443
&lt;UL&gt;&lt;LI&gt;The URL for the HTML5 Gateway will be the normal Privilege Cloud Web Portal, with ‘webaccess-’ at the beginning For example, the Gateway address for ‘customer.privilegecloud.cyberark.cloud’ would be ‘customer-webaccess.privilegecloud.cyberark.cloud’&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Thu, 05 Nov 2026 20:04:54 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T20:04:54Z</dc:date>
    <item>
      <title>Remote Access Prerequisites</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-articles/remote-access-prerequisites/ta-p/1428253</link>
      <description>This article has been created to help Customers Prepare for their Remote Access Deployment.

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;SPAN style="font-size: 16px;"&gt;&lt;STRONG&gt;What's needed.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;In preparation for the deployment day, there are a number prerequisites which need to be met, these consist of the following.
&lt;OL&gt;&lt;LI&gt;Issuing of Certificates.&lt;/LI&gt;&lt;LI&gt;Access to the Connector Servers and knowledge of the InstallerUser Credential.&lt;/LI&gt;&lt;LI&gt;Confirmed Admin Access to the PVWA Web Portal.&lt;/LI&gt;&lt;LI&gt;Access to the HTML5 Gateway Web Address on port 443.&lt;/LI&gt;&lt;/OL&gt;
&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 14px;"&gt;Issuing of Certificates.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;In the interest of the hosted HTML5 Gateway, each Connector Server is required to have its own Certificate issued by a Certificate Authority and placed into the Servers "Personal Certificate Store", Idira will also require a copy of the Root/Intermediate Certificate to upload into backend Idira Services.&amp;nbsp; When requesting the Certificate, the following requirements are needed.
&lt;OL&gt;&lt;LI&gt;&amp;nbsp;Strong Private Protection is not enabled.&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;Must include Server Authentication under "Intended Purposes"&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;Must contain the FQDN of the Connector Server under "Subject Name", please also select "Common Name" as the type.&lt;/LI&gt;&lt;LI&gt;If a Load Balancer is in use, then the FQDN of the NLB needs to be added as the "Alternative Name", please select "DNS" as the type&lt;/LI&gt;&lt;LI&gt;Upload a copy of the Root/Intermediate Cert&amp;nbsp;to your SFE safe.&lt;/LI&gt;&lt;/OL&gt;
&lt;BR /&gt;&lt;SPAN style="font-size: 14px;"&gt;&lt;STRONG&gt;Access to Connector Servers and knowledge of the InstallerUser Credential.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;On the day, we are required to add additional configuration into the Secure Tunnel that is hosted on each Connector Server, in order to do this, we require one of the Participants to have access to each server, we also require that a Participant is able to retrieve the InstallUser credentials, Note: This can be access from the Identity Admin Portal.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 14px;"&gt;Confirmed Admin Access to the PVWA Web Portal.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;During the validation testing of Remote Access, we will require one of the Participants to have Idira Admin access to the PVWA Web Portal and access to an Onboarded Account where they can add additional members to that Accounts Safe.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 14px;"&gt;&lt;STRONG&gt;Access to the HTML5 Gateway Web Address on port 443.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Confirmation that Remote Access users, will have access to the HMLT5 Gateway web address on port 443
&lt;UL&gt;&lt;LI&gt;The URL for the HTML5 Gateway will be the normal Privilege Cloud Web Portal, with ‘webaccess-’ at the beginning For example, the Gateway address for ‘customer.privilegecloud.cyberark.cloud’ would be ‘customer-webaccess.privilegecloud.cyberark.cloud’&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 05 Nov 2026 20:04:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-articles/remote-access-prerequisites/ta-p/1428253</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T20:04:54Z</dc:date>
    </item>
  </channel>
</rss>

