- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
06-24-2024 01:33 PM
Hello,
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.
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.
How can I make all AD users go through SAML authentication, just like Self-Hosted EPV?
Thanks you.
06-24-2024 02:24 PM
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.
https://community.cyberark.com/s/article/CyberArk-Identity-How-to-configure-or-restrict-attribute-matching-for-the-CyberArk-Identity-Connector
06-25-2024 07:14 AM
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?
07-02-2024 07:02 AM
Check the authentication profile under 'Settings > Authentication' and for your end-user profile remove everything except password.
Under 'Core Services > Policies' select the policy the user would be directed to and under 'Authentication Policies > CyberArk Identity' ensure the Default profile is the one you previously set to just password.
07-22-2024 07:07 AM
@Anderson Viotti 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.
07-29-2024 06:41 AM
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:
If anyone else is trying to set this up, I'm more than happy to assist.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

