Connectall Oauth 2 authentication for the Microsoft Adapters displays a different user than we expect as the creator of artifacts in Azure DevOps and Service Now
search cancel

Connectall Oauth 2 authentication for the Microsoft Adapters displays a different user than we expect as the creator of artifacts in Azure DevOps and Service Now

book

Article ID: 379429

calendar_today

Updated On:

Products

ConnectALL ConnectAll On-Prem ConnectAll SaaS

Issue/Introduction

To use the Oauth 2 authentication we need to register the ConnectALL application in Azure DevOps or Service Now.  The user that registered the Application is not displaying as the user that creates all the artifacts in Azure Devops.  Why?

Resolution

When creating a connection using a Microsoft product, the userid that is cached in the browser or that logs into Microsoft at the time of the connection creation will be the userid used to create any artifacts in the Microsoft product (Azure Devops, Service Now etc....).  The user that registered the application will not be used.

If you would like your ADO service account to be used we recommend opening ConnectALL in an incognito window and creating a new ADO connection to use.  At that time you will be prompted to login to ADO/Microsoft using the ADO service account.