Getting Oauth Token in Scope vs Global
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2024 06:38 AM - edited 07-26-2024 06:38 AM
I needed to create an Application Registry to get an Oauth Token from a third-party provider.
I defined the application registry and related the Oauth entity profile to a Oauth 2.0 credential.
I had all of this defined in a custom spoke - had issues getting a token.
I defined everything the same in Global, and had no had no issues getting a token.
Is there something missing? Why would setting up Oauth in a custom spoke have issues getting the token?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I ended up opening a case when I first encountered the issue.
It ended up being that my MID server user that was pulling the credentials didn't have the read permissions defined for my custom application. ServiceNow support recommended to have the registries and credentials setup in Global.