Orchestrator using old credential value

orchestrator

#1

We changed a password in one of our Orchestrator credential assets. The following scheduled executions faulted and we could not figure out why. We then discovered that the old password was still being used. Is this some sort of cache issue?


#2

Hey there,

Are you sure that was a credential asset? How were you able to see Secure String password value if so?

My point is that if you are storing the password on string asset instead of credentials asset then there is a possibility that it was hard coded somewhere.
Best regards!