<?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 Triggering the Secure Web Sessions (SWS) when accessing target web applications. in Idira General Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/idira-general-discussions/triggering-the-secure-web-sessions-sws-when-accessing-target-web/m-p/1394559#M524</link>
    <description>&lt;P&gt;Will the workflow below allow CyberArk Secure Web Sessions (SWS) to function correctly for target web applications accessed via JumpCloud?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note: This is an ISPSS environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Workflow access to the target web applications:&lt;/P&gt;&lt;P&gt;1. User requests access to a specific JumpCloud service account from CyberArk PAM.&lt;/P&gt;&lt;P&gt;2. Upon approval, the user clicks the JumpCloud tile from the CyberArk Secure Access portal.&lt;/P&gt;&lt;P&gt;3. CyberArk redirects the user to the JumpCloud portal landing page.&lt;/P&gt;&lt;P&gt;4. Once login, the user selects the web application within JumpCloud and performs SSO to the target web application. (Question: Does this step will initiate the SWS layer on the target web applications, such as recording?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Observation:&lt;/P&gt;&lt;P&gt;Based on testing, sessions initiated using this workflow, where the target web application is launched from the JumpCloud portal are not recorded by SWS; only the JumpCloud are recorded. My understanding is that SWS relies on being associated with specific application URLs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this behavior expected? Are there any additional configurations required?&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jan 2026 06:14:55 GMT</pubDate>
    <dc:creator>kweiwing_neng</dc:creator>
    <dc:date>2026-01-27T06:14:55Z</dc:date>
    <item>
      <title>Triggering the Secure Web Sessions (SWS) when accessing target web applications.</title>
      <link>https://live.paloaltonetworks.com/t5/idira-general-discussions/triggering-the-secure-web-sessions-sws-when-accessing-target-web/m-p/1394559#M524</link>
      <description>&lt;P&gt;Will the workflow below allow CyberArk Secure Web Sessions (SWS) to function correctly for target web applications accessed via JumpCloud?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note: This is an ISPSS environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Workflow access to the target web applications:&lt;/P&gt;&lt;P&gt;1. User requests access to a specific JumpCloud service account from CyberArk PAM.&lt;/P&gt;&lt;P&gt;2. Upon approval, the user clicks the JumpCloud tile from the CyberArk Secure Access portal.&lt;/P&gt;&lt;P&gt;3. CyberArk redirects the user to the JumpCloud portal landing page.&lt;/P&gt;&lt;P&gt;4. Once login, the user selects the web application within JumpCloud and performs SSO to the target web application. (Question: Does this step will initiate the SWS layer on the target web applications, such as recording?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Observation:&lt;/P&gt;&lt;P&gt;Based on testing, sessions initiated using this workflow, where the target web application is launched from the JumpCloud portal are not recorded by SWS; only the JumpCloud are recorded. My understanding is that SWS relies on being associated with specific application URLs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this behavior expected? Are there any additional configurations required?&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 06:14:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/idira-general-discussions/triggering-the-secure-web-sessions-sws-when-accessing-target-web/m-p/1394559#M524</guid>
      <dc:creator>kweiwing_neng</dc:creator>
      <dc:date>2026-01-27T06:14:55Z</dc:date>
    </item>
  </channel>
</rss>

