If we automate on a critical application that only allows one login with a credential pair at a time it is not possible to scale the process by running multiple instances of it at the same time. It is possible by deploying the same process again but with a different credential referenced in the config which somehow takes away flexibility and scaleability in my eyes.
Currently I cant find a good build in solution for that.
Maybe it would be possible to store multiple credentials in a way that a job of a process takes one of the available credentials and blocks it until the job that fetched it is completed. Other instances could then take different Credentials.
We could use queue to store multiple credentials and use it in the Re framework. But I am not sure whether it is secured or not.we have an option called credential store and we can use it using activity in workflow.
I think queues are not suiteable since they have a complete different purpose.
Not familiar with other credential stores since we use the default Orchestrator Database store for credentials but I assume that the problem would be the same with other credential stores.