- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
03-21-2019 04:29 PM
After lot of troubleshooting managed to enable client certificate based authentication for CCP. Able to access wsdl using a certificate from browser, however the SOAP/REST API script fails to send certificate.
Did anyone else face similar issue? Any thoughts on the solution?
Sample SOAP/REST script helps
03-28-2019 09:42 AM
Assuming all of the steps to Configure Client Authentication with client certificates have been completed.
In PowerShell, you should then be able to provide the relevant certificate details in your request using the "-Certificate" or "-CertificateThumbprint" parameters:
Invoke-WebRequest -CertificateThumbprint
Invoke-RestMethod -Certificate
etc
03-21-2019 08:29 PM
@Mohan Bandha what script are you using?
FYI.. The below steps I've followed for java based rest clients.
1. On board Required Application into CyberArk via Password Vault Web Access (PVWA) Web Portal.
2. Create Required Platform and Safe.
3. On-board Required Privileged Service Account into CyberArk via PVWA
4. Add Application created in step1 as the member of this Safe with Retrieve permission enabled
5. Add Provider Users as a member to the Safe, which was created as part of CCP initial installations.
6. Add the Certificate into CCP’s IIS server, the same certificate will be used for client authentication (Assume that you are going to use certificate authentication)
7. Add the certificate into java keys store using Java key tool command (Assume that your REST/Web Service clients are developed in java)
8. Run the java Code.
03-21-2019 10:38 PM
You may try using Soap UI. For sample script, you may refer to the link provided when you install AIM web service.
Post succesfull install on web service a hyper link appears- 'Get Password' and entire page opens for SOAP UI and REST calls.
Thanks,
03-21-2019 10:38 PM
You may try using Soap UI. For sample script, you may refer to the link provided when you install AIM web service.
Post succesfull install on web service a hyper link appears- 'Get Password' and entire page opens for SOAP UI and REST calls.
Thanks,
03-28-2019 07:31 AM
@hp thanks for the response. I have tested the web service and it works fine for the IP based authentication. I am working on enabling certificate serial number authentication and have enabled client SSL authentication on IIS. While I am able to open the wsdl page using the client cert when accessed from browser, running a powershell gives me access forbidden error.
Do you have any insights on enabling certificate authentication for CCP?
03-28-2019 09:42 AM
Assuming all of the steps to Configure Client Authentication with client certificates have been completed.
In PowerShell, you should then be able to provide the relevant certificate details in your request using the "-Certificate" or "-CertificateThumbprint" parameters:
Invoke-WebRequest -CertificateThumbprint
Invoke-RestMethod -Certificate
etc
03-28-2019 09:50 AM
@Pete Maan That is a good assumption 🙂 I am able to open the wsdl from a browser and it shows me the wsdl when a certificate trusted by the CCP server is used and gives a access forbidden error when a certificate that is not trusted by the CCP server is used. With this I assume that the 2 way SSL configuration is correct.
I am not able to invoke via script, tried powershell REST , powershell SOAP , Java SOAP and in all these cases, I get access forbidden error. I am kind of struck on where the issue could be.
I am using a self signed client certificate so far, requested for a CA issued client certificate and hoping that it would help me identify if the issue is with certificate.
On the IIS configuration itself, I have not enabled certificate one to one / one to many mapping. I do not see this as dependency as the certificate validation will be done by AIM. Is this is a valid assumption?
Many thanks
03-29-2019 03:10 PM
@Pete Maan Thanks for the reference.Configuring at AIMWebService level did the trick. In all my previous attempts, I was configuring at lower level v1.1. The new situation is that clientSSL works fine but default authentication does not work. Since client SSL is configured at AIMWebservice level, certificate has become mandatory. Do you have tips around allowing both clientssl and default authentication?
04-01-2019 02:16 AM
@Mohan Bandha - you can configure support for multiple security configurations:
04-01-2019 05:32 AM
@Pete Maan thanks for your tips and reference. The configuration worked fine. Apparently the issue of working with browser and not working in powershell was that , while I was opening a fresh browser session to check the connectivity, I was working on the same powershell prompt. The information in the link shared by you worked.
03-26-2020 02:29 AM
Hello Pete,
Currently we are also facing same issue.We have configured both client and windows authentication setup as per the cyberark guide.
But Enabling "Anonymous Authentication" in AIMWebservice, my client authentication works.But at the same time Windows authentication is not working.
I can see two folders under AIMWebservice in ISS . 1) V1.1 and 2) Win
Both we have configured according to certificate and windows authentication.
But still if we enable in AIMWebservice only certificate works, at the same time throws error for Windows and vice versa.
Could you please help me what could be the reason here.
Thanks,
Laxmi
03-27-2020 08:16 AM
Configure default AIMWebservice with certificate and win for windows. Ensure that in IIS, require SSL is disabled for win
03-30-2020 11:57 PM
Hi,
Thanks for the reply.I tried the solution you provided.But still same issue.
I raised case with CyberArk as well, where they confirmed the RestAPI no longer support multi security authentication.However SOAP Webservice request should work to handle both request at a time.
Thanks,
Laxmi
04-02-2020 03:03 PM
@Laxmipriya Nayak . Sorry to hear it did t work. In our case it was the other way around. REST API works for multi security authentication, while SOAP doesn't work.
Let me know how it goes.
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!

