from an external vault (Secret Server), where a company already manages the credentials for users
the passwords potentially change daily so it’s not feasible to manage them in every local machine
At least the first bullet could have activities developed in UiPath
We are planning a Cyber Ark Orchestrator integration in the next release. This will open the possibility to add other Vault providers in the future.
Estimated 2017 Q3 or 2018 Q2. It’s hectic here and we can not actually estimate the difficulty of the feature now now.
Are you going to use this to retrieve and store:
Windows Login Credentials for robot
Third Party Apps Credentials like SAP Login
or both?
If your use case is only the second (3rd party) this can be achieved via creating custom activities - Orchestrator integration is not necessarily needed and it can be achieved by a .NET dev or an advanced forum user.
I juts came across this use case.
What of in a scenario where the Third App need a login that is stored in a 3rd party credential store that has an API exposed to retrieve credentials?
Secret Server has an API that you can call via HTTP requests. You could build out some UiPath modules to take advantage of those API calls for existing credential vaults. You may have to parse the response strings in a few places or construct the HTTP request rather than using the default Uipath activities, but it’s a doable task.
You can find the specific API calls by going to your local secret server web address like the following:
https://{your-local-secret-server-address}/SecretServer/webservices/SSWebservice.asmx
You can find more documentation similarly at the following:
https://{your-local-secret-server-address}/SecretServer/Documents/restapi/
I developed the credential store pugin for secret server in orchestrator but when I clicked on create button after filling all the details it gives me an error : Invalid Credential Store configuration. (#2303)
Hi Shahid, did you find any solution for this.
I am getting the following error
Invalid Credential Store configuration. Reason: Operation ‘get-access-token’ failed. External Response:
{
“errorCode”: “API_RuleDoesNotMatch”,
“message”: “The onboarding rule does not match.”
} (#2303)