<?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: Active Directory + SAML in Workforce Identity Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411069#M1815</link>
    <description>&lt;P&gt;Thank you all for your assistance. I was struggling to find the best and most secure way to integrate Active Directory with Privilege Cloud and the external IdP (Okta), so I'm sharing what I did to help others:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Disabled the Default Policy for all users and applied it only to a few administrator roles so that they can login with their CyberArk Cloud users. I set it on top.&lt;/LI&gt;&lt;LI&gt;Created a 'Block' authentication policy (a role with no factor) and applied to "All Users".&lt;/LI&gt;&lt;LI&gt;This policy does not block authentication via external IdP/SAML, as it follows a different path. I created a redirect rule, so when users type their e-mail, they are redirected to Okta for authentication, and in the backend they are mapped to their AD uses.&lt;/LI&gt;&lt;LI&gt;Now users can only login with their e-mail addresses and external IdP. If they type their AD username, their authentication will be blocked right away.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If anyone else is trying to set this up, I'm more than happy to assist.&lt;/P&gt;</description>
    <pubDate>Mon, 29 Jul 2024 13:41:54 GMT</pubDate>
    <dc:creator>anderson.viotti</dc:creator>
    <dc:date>2024-07-29T13:41:54Z</dc:date>
    <item>
      <title>Active Directory + SAML</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411064#M1810</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am integrating Identity with Active Directory. I also added an "External Service Provider" for SAML authentication, and created a routing rule so that when AD users type their e-mails, they are redirected to the External IDP (Okta) authentication page.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, if I login using other AD user attributes rather than the e-mail, for example, my user ID, Identity asks to send me a MFA code to my e-mail (CyberArk built-in MFA I think) and does not use SAML.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can I make all AD users go through SAML authentication, just like Self-Hosted EPV?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks you.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2024 20:33:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411064#M1810</guid>
      <dc:creator>anderson.viotti</dc:creator>
      <dc:date>2024-06-24T20:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory + SAML</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411065#M1811</link>
      <description>&lt;P&gt;The Identity Connector will attempt to match the UPN, email, and sAMAccountName when a user authenticates. Setting up the domain rule in your eIDP configs will "trump" this attempt for the domain suffix(es) in question. You can keep the user from logging in with sAMAccountName (or UPN if needed) using the instructions in link below. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/CyberArk-Identity-How-to-configure-or-restrict-attribute-matching-for-the-CyberArk-Identity-Connector&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2024 21:24:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411065#M1811</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-06-24T21:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory + SAML</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411066#M1812</link>
      <description>&lt;P&gt;Jamie, thank you very much your help. I was really hopping the keys would do the trick, but it did not work. It's interesting that if I type anything (a user ID that does not even exist in AD/CyberArk Cloud), Identity somehow links this to someone's e-mail / phone number instead of blocking the authentication or giving a message. I type a real username (sAMAccountName) users would not be redirected my to IDP and bypass strong MFA factors. Any suggestions?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Ht00000VcNtEIAV.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/89091i0A4BC4F8C4A3D44E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Ht00000VcNtEIAV.png" alt="Field_Content_versions_oct20__068Ht00000VcNtEIAV.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2024 14:14:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411066#M1812</guid>
      <dc:creator>anderson.viotti</dc:creator>
      <dc:date>2024-06-25T14:14:04Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory + SAML</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411067#M1813</link>
      <description>&lt;P&gt;Check the authentication profile under 'Settings &amp;gt; Authentication' and for your end-user profile remove everything except password.&lt;/P&gt;&lt;P&gt;Under 'Core Services &amp;gt; Policies' select the policy the user would be directed to and under 'Authentication Policies &amp;gt; CyberArk Identity' ensure the Default profile is the one you previously set to just password.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2024 14:02:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411067#M1813</guid>
      <dc:creator>switzer</dc:creator>
      <dc:date>2024-07-02T14:02:56Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory + SAML</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411068#M1814</link>
      <description>&lt;P&gt;@Anderson Viotti​&amp;nbsp;My apologies that I had some PTO starting the day you posted this and never saw the reply, but that sounds like either a permissions issue or a bug.  I believe it would be very random indeed if you were picking attributes that were actually associated with a true user in your AD. Would you consider opening a support ticket with repro steps so they can investigate.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2024 14:07:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411068#M1814</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-07-22T14:07:15Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory + SAML</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411069#M1815</link>
      <description>&lt;P&gt;Thank you all for your assistance. I was struggling to find the best and most secure way to integrate Active Directory with Privilege Cloud and the external IdP (Okta), so I'm sharing what I did to help others:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Disabled the Default Policy for all users and applied it only to a few administrator roles so that they can login with their CyberArk Cloud users. I set it on top.&lt;/LI&gt;&lt;LI&gt;Created a 'Block' authentication policy (a role with no factor) and applied to "All Users".&lt;/LI&gt;&lt;LI&gt;This policy does not block authentication via external IdP/SAML, as it follows a different path. I created a redirect rule, so when users type their e-mail, they are redirected to Okta for authentication, and in the backend they are mapped to their AD uses.&lt;/LI&gt;&lt;LI&gt;Now users can only login with their e-mail addresses and external IdP. If they type their AD username, their authentication will be blocked right away.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If anyone else is trying to set this up, I'm more than happy to assist.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 13:41:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/active-directory-saml/m-p/1411069#M1815</guid>
      <dc:creator>anderson.viotti</dc:creator>
      <dc:date>2024-07-29T13:41:54Z</dc:date>
    </item>
  </channel>
</rss>

