- 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-02-2019 06:20 AM
Trying to set up AppID to use OS User authentication. Our basic idea is to execute playbooks with specific service accounts that are authorized in the AppID to pull the credential. We can make OS User called using PowerShell and -UseDefaultCredential but the OS User isn't passed in the playbook without explicitly coding the credentials which we are trying to avoid. Any tips on setting this up? Or has anyone else come up with creative ideas for playbook AppID authentication?
10-02-2019 06:44 AM
Has Windows Domain Authentication been configured for CCP?
After that configuration has been put in place, there are additional steps required for the REST API (as the documentation relates only to the SOAP API):
Detailed here: https://community.cyberark.com/s/article/CCP-AIMWebService-Windows-Authentication-not-working
For the PowerShell point, there are two ways to send credentials: either by specifying a credentials object, or by Using the default credentials.
Do you notice any difference if specifying a credential object instead of using the -UseDefaultCredential switch parameter?
10-02-2019 06:53 AM
Hey Pete,
Got all this working. I can make a test call from PowerShell and validate OS User. More specifically I am interested in getting this to work in an Ansible playbook. Concerns are that if we authorize strictly based on IP, different playbooks can call all the credentials authorized for that host. I'm starting to think passing certificates in the playbook and authorizing those may be a better approach as I don't see an easy way to do Windows Auth in an Ansible playbook
10-02-2019 07:43 AM
My mistake, just re-read your post and that is all explained!
There are these examples from CyberArk, https://github.com/cyberark/ansible-modules, but they do not include OSUser. Certificate auth would work - as shown in Example 7 on that link.
11-29-2019 02:40 PM
Thanks for that link. Would you be able to help me understand how exactly can I prevent my Oracle team from using credentials for my Windows team? Each team has their own playbooks. What prevents them from using the cert for another team when they are hosted on the same Ansible tower? Most of the information is easily discovered. Is it just the S/N lookup bound to a unique APP ID?
12-04-2019 06:32 AM
@Joe Garcia has an Ansible webinar coming up which may be of interest/help: https://lp.cyberark.com/Ansible-Automation_Registration.html
12-04-2019 06:34 AM
Thanks very much for this reply! perfect timing
12-04-2019 06:48 AM
@Joe Garcia Will this focus more on conjur than AAM or does it even matter? Just pure and simple how to prevent credential snatching? 🙂
12-04-2019 07:21 AM
If you're using Ansible Tower, it has a security feature called "Job Isolation". This will prevent the Credential Provider from being able to read attributes such as OSUser, Path, etc. It is enabled by default and would need to be disabled to utilize those attributes as part of AppID authentication.
12-04-2019 07:23 AM
Looks like you're using Centralized Credential Provider (CCP) which does not support OSUser. Only Whitelist Machines and Certificate Serial Number (Client Certificate Authentication).
12-04-2019 07:23 AM
It focuses on everything CyberArk does with Ansible... not just one product or another.
12-04-2019 07:26 AM
Actually we will be using a dedicated provider so I'm hoping to get a wrapper made in my next sprint so it is available to all playbooks in a "job isolated" manner. This with all available CyberArk authentication controls I can to ensure it is secure. Thanks very much for this information.
12-04-2019 10:21 AM
Hey,
Thanks for the reply. We ended up going with certificate auth - assigning certificates to our respective playbooks. With that being said, it is possible to use OS User with the CCP. I was able to validate pulling credentials from the CCP using OS User and PowerShell in the past... there are some KB articles on it. It is supported, I think you can do it with the win uri ansible modules but we ended up taking another path
02-18-2020 03:40 AM
@Joe Garcia ,
we are trying to integrate Ansible tower with CCP. our CP/CCP server has Windows+Certificate authentication enforced at IIS level. how can we achieve the integration in this case? I believe there is no User / Password related attributes in Ansible configuration. What's the best approach in this case ?
TIA
10-28-2020 01:15 AM
@infamousjoeg (CyberArk) Hey Joe could you clarify this, I presume you mean OSUser is not supported for CCP specifically in relation Ansible playbooks? Surely CCP has generally been supporting OSUser for both REST and SOAP for a long time.
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!

