- 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2021 01:36 AM
Hi Team,
I am getting the error while accessing Oauth access token from servicenow instance as below
{"error_description":"access_denied","error":"server_error"}
I have created OAuth End Point on another instance having below client_id and client_secret
URL = https://customer_instance.service-now.com/oauth_token.do
client_id = 0fa6dade7b000110abfbf53e56d948ff
client_secret = ]Uvyq{wfz`
Content-type = application/x-www-form-urlencoded
grant_type = password
with username & password
I checked the username and password by using /login.do and it's working so I think my password is correct
Please do the needful