OAuth token fetching via MID is supported (only for Client Credentials grant type)SummaryUntil the Washington release, ServiceNow did not support fetching OAuth tokens via the MID server. However, ServiceNow did support accessing the resource server via the MID server using OAuth. Starting with the Washington release, ServiceNow began supporting OAuth token fetching via the MID Server. However, this support is currently limited to the Client Credentials grant type. Additionally, it is available only for the Flow Designer REST Step(IntegrationHub), not for REST Message.ReleaseWashingtonInstructionsHere are the steps to configure OAuth token fetching via the MID Server. 1. Navigate to "System OAuth -> Application Registry." 2. Click on "New." 3. Click on "Connect to a third-party OAuth Provider." 4. Fill out the form with the information received from the OAuth Provider. 5. Select "Client Credentials" as the "Default Grant type." 6. Save the record with all the required information. 7. Navigate to "Connections & Credentials -> Credentials." 8. Click on "New." 9. Select "OAuth 2.0 Credentials." 10. Configure the Name. 11. Click on the magnifying glass in "OAuth Entity Profile" to look up using the list. 12. Choose the OAuth Entity Profile created in the previous steps. 13. You will see a new option on the form, "Connect to Auth Server via MID Server." Check this checkbox. 14. Change the "Applies to" field to "Specific MID Servers." 15. Choose a MID server that is currently up and running. Note: The selected MID Server must have REST capabilities. 16. Click on Submit. The setup is ready, follow the below steps to test it: 1. After clicking "Submit," you will see a message at the top: "OAuth Access or Refresh tokens are not available. Verify the OAuth configuration and click the 'Get OAuth Token' link below to request a new token." 2. Click on the "Get OAuth Token" related link. 3. A popup will open, displaying the message "OAuth token flow completed successfully." 4. When you click "Get OAuth Token," the system creates an output record in the ecc_queue table with the topic as "RESTProbe" and the source as "token endpoint." 5. The MID Server picks up the output record, communicates with the token provider, and responds back with an input record. 6. You can see a token in the oauth_credential table. Additionally, you will see the message "Error Message: OAuth Access token is available but will expire soon at..." on the credential record. Related LinksRefer below documentation for more information: https://docs.servicenow.com/bundle/washingtondc-platform-security/page/product/credentials/reference/oauth-2-credentials.html