Why is the robot failing to log in with a disconnected credentials proxy?
Issue description:
The robot is failing to log in with disconnected credentials proxy.
Troubleshooting and Resolution steps:
When launching a job, it errors out with a 404 - Not found error message:
If the error 404 cannot be seen in the logs of the machine where the Orchestrator Credentials Proxy is installed, it means that the API call doesn't reach there, and that the setting in Orchestrator needs to be checked.
Issue was resolved after adding the correct key under the Credential Store configuration in the Orchestrator Web Interface.
In the Credential Store section in Orchestrator, in the key field, the value to put here is actually the key of the credential store, under the SecureStoreConfigurations in the appsettingsProduction.json, which is the name of your Store:
"SecureStoreConfigurations": [
{
"Key": "<MyXXXXStore>",
"Type": "xxxx (read only)",
"Context": {
"KeyVaultUri": "<KeyVaultUri>",
"DirectoryId": "<DirectoryId>",
"ClientId": "<ClientId>",
"ClientSecret": "<ClientSecret>"
}
},
]
Which means that both Name and Key in the Credential Store configuration have the same value:
And in the Credentials Proxy section, in the key field, the JWT token of the appsettings.production.json is needed:
