Hi Augustin,

How did you resolve the issue mentioned above? I'm encountering the same problem during authentication.

{"code":"cv.validation.credential.not.found","correctiveAction":"It may have been renamed or deleted. If the problem persists, please contact your system administrator.","details":"","message":"The credential wasn't found."}

Hi Diva 6381,

The problem has not been solved to this day.

Did you find solution there : https://docs.automationanywhere.com/bundle/enterprise-v2019/page/integration-oauth-control-room.html and  https://apeople.automationanywhere.com/s/article/Automation-360-cv-validation-credential-not-found-Cannot-create-OAuth-related-locker-starting-with-OAUTH ?

In my case, it works correctly for a few minutes, then fails.

But I remember that the same message appears when there is a security configuration error.

Hello ​@Augustin , ​@Diva 6381, I’m facing the same issue to keep my token from refreshing every few minutes. I am trying to access GMail Oauth API and this is a blocker for me. Were you able to resolve this error?

​

Hi ​@AKPRTH  sadly I did not find a solution. I used the bot-managed connection and not the control-room managed connection.

Please check the below KB article where a similar issue is documented along with the solution.

https://apeople.automationanywhere.com/s/article/A360-Issue-with-Control-Room-OAuth-Connection-Token-Renewal-for-SharePoint-or-other-applications

Hello,

I have the same issue as described above. I have checked KB article that shared above and we have scope determined as https://<domain-name>/AllSites.Manage, offline_access, openid in our oauth configuration. However every day I need to re-test oauth connection to switch from “Expired" to “Active” shared token status and after I can run the bot successfully only once - it needs to be within a couple of minutes time range. After the connection does not work anymore even though the oauth connection shows Active Status. Can anyone please help? Thank you

Please try modifying the scope to  AllSites.Manage offline_access and then click on test connection to see if it fixes the issue.