Azure OAuth Refresh Token Not Renewing Automatically
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Our ServiceNow instance uses Azure OAuth 2.0 for both inbound IMAP and outbound SMTP email processing.
We have observed that access tokens are being renewed automatically, however, the refresh token is not being renewed or rotated after expiry, even though the offline_access scope is added in the OAuth Entity Profile.
Please help identify if any additional Azure or ServiceNow configuration is required to support automatic refresh token renewal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago - last edited 3 hours ago
Its some wired scenario.
Do one thing. From managed token, whatever token you generated for this Oauth profile/connection , delete it.
Validate offline_access scope setting once. Then generate the token.
Observe if after 1 hour , token is getting expired or not.
Update what you are getting.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
58m ago
Since this is a PROD environment, I’m unable to delete it. Also, this configuration was not set up in the lower environments. Is there any alternative approach we can use?
Anything we can check it in Azure side? @Tanushree Maiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
52m ago
open the set up documentation and ensure Azure team has provided correct credential with required permission as per the ServiceNow documentation.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
48m ago
@Tanushree Maiti If some configuration is wrong then access token also should not work right? here, access token is working fine.. issue is only with the refresh token