We have an Orchestrator on-prem installation and we’re trying to setup the integration with Secret Server, also on-prem.
However, although we followed all recommended steps (UiPath Overview and from the official UiPath documentation), the creation of the Credential Store doesn’t seem to work:
We already checked all the basic steps (we redid all the steps from the documented procedure more than once, we ensured that the Orchestrator server can reach the Secret Server site - so we safely excluded network issues), etc… but we can’t seem to figure out where the issue comes from.
Has anyone experienced the same issue and can help me out?
Indeed, the infra team managed to find the root cause of the issue, which was more related to our server configuration for Secret Server and not at all to UiPath.
I must admit that I only have vague memories about it, but if I remember correctly it was an issue with the Integrated Windows Authentication, or maybe something about an Autologon setting.
On this link you’ll find this:
The SDK is designed to be used as it is shown below and is not designed to be run using IWA to retrieve tokens or Secret information. Given this, the SDK is not supported with IWA.
And it’s likely that this was our issue. We ended up dropping completely the idea of an integration with Secret Server.
What brought us towards the good investigation direction was the fact that we tried using directly the SDK to retrieve a secret, and we received the same error message that we were getting in Orchestrator. With this, we could safely exclude that the issue was related to UiPath, and we continued the investigation with the Delinea support.
