Setup ServiceNow Azure DevOps Agile Development and Change Velocity Connections using OAuth?

Dustin24
Tera Contributor

Does anyone know or had any success with setting up an OAuth connection between ServiceNow/Azure DevOps? Specifically this is for the Agile Development 2.0 and Change Velocity Integrations. Guided setup docs say to setup using Basic Authentication using PATs in DevOps, but I cannot find anything anywhere stating this is the only supported method. I'm opposed to using PATs for these connections since it requires at minimum an annual renewal. Additionally using a PAT for the Agile Development 2.0 Unified Backlog integration, any stories created in ServiceNow are also creating the work items in ADO, but the created by in ADO is always reflecting as the owner of the PAT regardless of who creates them in SNow. I would expect that the created by in ADO should reflect the created by user in ServiceNow, but this is not the case.

2 REPLIES 2

V V Satyanaraya
Tera Contributor

Hi Dustin,

I have configured same type of connection, and comments are updating with username who has created access token for us. Did you find any work around for this ?

Also there are few issues like work notes updating with <div> tags in ServiceNow and multiple work items are creating some times at ADO. Is it the same kind of expected behaviour? 

 

Regards,

Satya

 

Sara3
Giga Guru

I am attempting this and have submitted Support tickets for it, but I'm also having issues when trying to set it up.  I did receive this information from SN Support in case it helps anyone else.  We are still having errors when trying to Connect to Azure DevOps after successfully getting an Oauth token.


Response from ServiceNow Support regarding whether the ADO/SAFe Integration will support Oauth:

 

I checked with our SME Team..
If Microsoft supports OAuth for Azure DevOps , then we can configure OAuth credentials in spite of Basic Auth.

Please see https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth?view=azure...
If you scroll down little bit you will see this note:

The following guidance is intended for Azure DevOps Services users since OAuth 2.0 is not supported on Azure DevOps Server. Client Libraries are a series of packages built specifically for extending Azure DevOps Server functionality. For on-premises users, we recommend using Client Libraries, Windows Auth, or Personal Access Tokens (PATs) to authenticate on behalf of a user.

Since OAuth is not supported by Microsoft Azure DevOps , we need to use Basic Auth..

Further checking , the basic Auth is only if you are on Prem, if not you can configure OAuth..
But, You should follow the above docs on how to enable OAuth for Azure DevOps application and then you can configure OAuth application registry and use that in credential table and use that credential when making API call to Azure DevOps

REF: https://docs.servicenow.com/en-US/bundle/tokyo-application-development/page/integrate/outbound-rest/...