- 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.
10-30-2023 04:55 PM
Hello. I would like to know whether the DPA supports authentication and authorisation to workloads using active directory accounts? Thanks
10-31-2023 04:30 AM
Gotcha, I think I better understand your question. At this point DPA only works with local accounts on Linux (existing accounts) and Windows (ephemeral.) I believe AD is on the roadmap.
10-31-2023 01:36 AM
Take a look at https://docs.cyberark.com/DPA/Latest/en/Content/CoreServices/UsersRoles/Add-users-DPA.htm?tocpath=Setup%7CAdd%20users%20and%20roles%7C_____1
10-31-2023 04:09 AM
Thanks Tim. I have gone through this link earlier and was trying to understand whether its mention about authenticating to target systems/workloads in Cloud by adding AD user (hosted in customer's premise) to workload and removing using JIT. Its still not clear to me whether its possible or not. Yes, we can leverage AD identity to authenticate to CyberArk Identity but not sure whether DPA will add AD account to workload and remove it later using policy defined in DPA.
10-31-2023 04:30 AM
Gotcha, I think I better understand your question. At this point DPA only works with local accounts on Linux (existing accounts) and Windows (ephemeral.) I believe AD is on the roadmap.
11-02-2023 02:12 AM
Hi @Malhar Vora ,
As @Tim Schindler mentioned for Windows, DPA currently creates ephemeral local account on the Windows targets and connects with the ephemeral local account (which we delete from the target after the session ends).
For Linux (SSH), we support local account as well as domain accounts. In our SSH solution, you define which target account should be used during connection to the target (in the access policy) and DPA creates an ephemeral SSH certificate for that specific session, which is then used to connect to the target. The target user needs to exist on the target machine, either as a local user or it can be provisioned\de-provisioned from a domain via an AD Bridge solution or alike if you have one.
You can see in our online help how to configure in the policy, that the connection will be with an AD user (we call it personal user in the documentation), please refer to: Create a recurring access policy > create an access rule > Profile (you can use the personal user format for local or domain accounts).
Hope that helps.
Hila
11-02-2023 03:49 AM
Hi @Hila Lepkifker Thanks for the clarification. Is provisioning / de-provisioning of AD accounts to target host planned for Windows EC2 instance?
11-02-2023 06:32 AM
Hi @Malhar Vora, thanks for this question.
We are considering to provide Just-in-time access to domain accounts (not sure yet about the exact method - if we will support provisioning of AD accounts or add domain users to predefined AD groups in Windows targets).
What method would you prefer and why?
If this might help, we are planning to have in our near term roadmap (H1 2024) a Just-in-time elevation of a PrivCloud vaulted account (which can be a domain account).
Please let us know if you would like more details.
Thanks,
Ronit
11-25-2023 04:11 PM
Thanks @Ronit Markovitz
The AD based accounts are most common Use case to authenticate to cloud workloads. Hence I was curious whether this feature is being planned.
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!

