<?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 CyberArk Secure Browser – Forcing Identity WebApp Profile Credentials on Launch in Workforce Identity Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387083#M1244</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We’re encountering an issue where &lt;B&gt;CyberArk Secure Browser&lt;/B&gt; is launching Microsoft admin portals using the &lt;B&gt;logged-in user’s credentials&lt;/B&gt;, rather than the account defined in the &lt;B&gt;Identity WebApp profile&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We suspect this behavior is influenced by Chromium policies — specifically:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;AuthNegotiateDelegateAllowlist&lt;/LI&gt;&lt;LI&gt;AuthServerAllowlist&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We’re looking for guidance on how to &lt;B&gt;configure these policies within CyberArk Secure Browser&lt;/B&gt; to ensure the correct identity is used on launch.&lt;/P&gt;&lt;P&gt;Any insights or examples from your experience would be greatly appreciated!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt; Siva&lt;/P&gt;</description>
    <pubDate>Thu, 09 Oct 2025 01:58:23 GMT</pubDate>
    <dc:creator>S.Mulpuru</dc:creator>
    <dc:date>2025-10-09T01:58:23Z</dc:date>
    <item>
      <title>CyberArk Secure Browser – Forcing Identity WebApp Profile Credentials on Launch</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387083#M1244</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We’re encountering an issue where &lt;B&gt;CyberArk Secure Browser&lt;/B&gt; is launching Microsoft admin portals using the &lt;B&gt;logged-in user’s credentials&lt;/B&gt;, rather than the account defined in the &lt;B&gt;Identity WebApp profile&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We suspect this behavior is influenced by Chromium policies — specifically:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;AuthNegotiateDelegateAllowlist&lt;/LI&gt;&lt;LI&gt;AuthServerAllowlist&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We’re looking for guidance on how to &lt;B&gt;configure these policies within CyberArk Secure Browser&lt;/B&gt; to ensure the correct identity is used on launch.&lt;/P&gt;&lt;P&gt;Any insights or examples from your experience would be greatly appreciated!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt; Siva&lt;/P&gt;</description>
      <pubDate>Thu, 09 Oct 2025 01:58:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387083#M1244</guid>
      <dc:creator>S.Mulpuru</dc:creator>
      <dc:date>2025-10-09T01:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: CyberArk Secure Browser – Forcing Identity WebApp Profile Credentials on Launch</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387084#M1245</link>
      <description>&lt;P&gt;Hi @Siva M​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To resolve this, you will need to configure the Chromium policies (AuthNegotiateDelegateAllowlist and AuthServerAllowlist) and to exclude Microsoft admin portals' URL.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is to ensure that browser doesn't automatically offer the user's logged-in Windows credentials to the Microsoft portal but allows vaulted credentials instead.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Oct 2025 03:25:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387084#M1245</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-10-09T03:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: CyberArk Secure Browser – Forcing Identity WebApp Profile Credentials on Launch</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387085#M1246</link>
      <description>&lt;P&gt;&amp;nbsp;@Malhar Vora​. My question was specifically about how to configure this for &lt;B&gt;Secure Browser&lt;/B&gt;, since I don’t see a relevant PolicyPak or setting available in SWS. Could you please advise if there's a different approach or if I'm missing something?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Oct 2025 12:04:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387085#M1246</guid>
      <dc:creator>S.Mulpuru</dc:creator>
      <dc:date>2025-10-09T12:04:42Z</dc:date>
    </item>
    <item>
      <title>Re: CyberArk Secure Browser – Forcing Identity WebApp Profile Credentials on Launch</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387086#M1247</link>
      <description>&lt;P&gt;Hi &lt;A alt="https://community.cyberark.com/s/profile/0052J000009JOp9QAG" href="https://community.cyberark.com/s/profile/0052J000009JOp9QAG" target="_blank"&gt;smulpuru&lt;/A&gt;, were you able to address this concern? we are also facing the same issue and looking for a solution. &lt;/P&gt;</description>
      <pubDate>Tue, 28 Oct 2025 07:29:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387086#M1247</guid>
      <dc:creator>Adhi_G</dc:creator>
      <dc:date>2025-10-28T07:29:52Z</dc:date>
    </item>
    <item>
      <title>Re: CyberArk Secure Browser – Forcing Identity WebApp Profile Credentials on Launch</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387087#M1248</link>
      <description>&lt;P&gt;@Adhiseshan Gunasekaran​&amp;nbsp;still looking for an answer. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CyberArk Team, looks like this needs to be added to SWS policies groups. Could someone chime in? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy00000wZKb7IAG.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/94093iC97FB026620B0D68/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy00000wZKb7IAG.png" alt="Field_Content_versions_oct20__068Vy00000wZKb7IAG.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy00000wZyePIAS.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/94101i454090056F10643F/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy00000wZyePIAS.png" alt="Field_Content_versions_oct20__068Vy00000wZyePIAS.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Oct 2025 13:12:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/cyberark-secure-browser-forcing-identity-webapp-profile/m-p/1387087#M1248</guid>
      <dc:creator>S.Mulpuru</dc:creator>
      <dc:date>2025-10-28T13:12:41Z</dc:date>
    </item>
  </channel>
</rss>

