- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
11-15-2019 04:40 AM
Good morning,
We are having an issue where a RPA application is using CCP to retrieve credentials from CyberArk. It works great until the CPM changes the password. The RPA application then starts getting a "incorrect username and password" error even though I can verify that the password in the vault is correct and works.
Any ideas what could cause this? Could it be a caching issue on the CCP?
Thanks,
Chris
11-15-2019 05:02 AM
hello @Chris Hartsock ,
generally with CCP, there won't be caching issues. but depending on the application credential handling, your application might be using the old password after CPM changes it.
does the application gets the password and assigns it to a variable for use? does it request for the password everytime it will use the password? (it should). If it does not this might be the cause of your problem.
Best Regards,
11-19-2019 09:43 AM
@Chris Hartsock what is refreshcacheinterval time period ? (I.e how often backgroundrefresh job occurs , 180 sec Default ?)
11-20-2019 08:30 AM
Thank you all for your feedback. It helped eliminate caching as the possible issue.
After digging deeper, it turns out the issue was on the RPA application side. The application was mishandling certain characters; specifically backslashes(\). For example, an account's password was "Cyberark\1. But when the application retrieved it and passed it to the end system it escaped the backslash. So it was ultimately trying to log in with "Cyberark\\1", and obviously failing. They made a configuration change on their side and it resolved the issue.
Thanks,
Chris
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!

