OAuth provider, profile migration to upstream instances and best practice to update "OAuth profile"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2023 11:03 PM
I have the following integration requirement:
Consumer: ServiceNow (Environment: DEV, TEST, PROD)
Provider: MuleSoft (DEV, TEST, PROD)
Authentication type: OAuth 2.0
Scenario:
We are consuming MuleSoft API by sending Outbound REST calls from ServiceNow using OAuth 2.0 authentication. The Client ID, Client secret and Token URL is different for all MuleSoft environment. We have created three different OAuth provider records in Application registry (oauth_entity) table. We don't have any problem obtaining access token. We would like to get suggestions on the below questions:
1. What is the best approach to populate "OAuth profile" field in the REST Message in TEST and PROD?
2. What is the best approach to configure REST messages in a way so it is easily testable in TEST and PROD?