- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2021 02:03 PM
I had the same issue and this link really helped me. https://www.linkedin.com/pulse/servicenow-outbound-web-services-oauth-20-how-handle-r%C3%A9da-osseili/
The error that SN returned by default is very misleading since it hides the actual detailed error message. We need to add some logs in the script include (OAuthUtil) that parse the get token response, so we can understand the exact issue.
My particular issue was that I was using the wrong client secret. I used the id instead of the actual secret value. Silly me, I know!
Once you enable the log in OAuthUtil, The error message was able to lead me to resolve my issue.
Hope this will help someone in the future.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2021 07:33 AM
Thanks for your comment Shawna, it helped in resolving my issue. This exactly happened to me, I did not use the actual secret values, but rather was using the client secret id.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2023 04:18 AM
Thanks for this. Funny how i made this exact mistake now. Used the secret ID instead of secret value.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2025 09:36 AM
Same error, like mentioned above the wrong secret was provided.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2021 09:54 AM
Hi there,
"I have the exact same setup for my dev instance"
Have you checked the settings within Intune itself? Recently I've been working also on Intune, and you have to specify the exact environment you are granting access too.
Kind regards,
Mark
