not able to click edit and get oauth token in the azure devops board spoke
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2025 05:51 PM
Hi, I am trying to configure Azure devops board spoke using oauth and in the outbound connection added all the details mentioned in the screenshot. i got them verified with client. But when I click on edit and get oauth token, nothing happens. Looks like the button is frozen. Can you help if I am missing something?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2025 06:53 PM
Hello @archie5
Can you check in your Oauth profile that the Authorization URL and Token UTL are provided correctly ?
Example URLs for Azure DevOps:
Authorization URL:
https://login.microsoftonline.com/{tenant_id}/oauth2/authorize
Token URL:
https://login.microsoftonline.com/{tenant_id}/oauth2/token
Also check for permissions within Azure Secops - where you did App registration - you are having sufficient access.
Kindly mark my answer as helpful and accept solution if it helped you in anyway,
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwN
eEISQCY
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2025 07:43 AM
Hi @archie5,
I would try the following:
- Navigate to Application Registry (System OAuth > Application Registry), and look for Azure DevOps OAuth. Ensure the Client ID, Client Secret, and Redirect URL match the values in Azure DevOps.
- Ensure redirect URL matches Azure DevOps settings. In Azure Portal, navigate to App Registrations (Azure Active Directory > App Registrations). Under Authentication, verify that the Redirect URL matches what is in ServiceNow.
- Check network traffic in your browser. Open Developer Tools (F12), go to the Network tab, click the "Edit and Get OAuth Token" button, and look for any failed requests to /oauth_token.do or /sn_auth.do. If you see 403 or 500 errors, there may be a permissions issue.
- Ensure you have the required roles: admin, oauth_admin, sn_ih_spoke_user (for IntegrationHub)
- Try using a different browser or incognito mode
Best,
Connor Lyons
Consultant at Infocenter
CSA | CAD | 16x CIS
Please mark answer correct and/or helpful for others reading this with the same issue/question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-16-2025 03:28 AM
Hello @archie5 ,
Could you please let us know, if you got this fixed. We are facing the same issue.
Thanks!