If you are using token-based authentication (TBA) in your sandbox and production account, be aware of the following:
The Token Key and Token Secret used for TBA are always different in each account.
The Token Key and Token Secret are deleted in your sandbox account after each sandbox refresh, and you must regenerate them. This has no impact on the Token Key and Token Secret used in your production account.
The Consumer Key and Consumer Secret can be shared between your sandbox and production accounts if you create an integration record in one account and install it on the other one. In this case, if you regenerate the Consumer Key or Consumer Secret in your sandbox account, they will be automatically changed in your production account and this can break your production account integrations.
Create a separate integration record in each account to avoid changes in the production account when credentials are regenerated in a sandbox account.
If you decide after testing that you need to make changes to an integration record, create a new record in your production account with those changes.
Not recommended practice:
Do not create new integration records if you only need to change the settings of an existing integration record or only need to regenerate authentication credentials. Instead, make changes on an existing integration record in your sandbox account and then install the integration record in your production account.
- Integration Management
- Integration Record Overview
- Adding an Integration Record
- Application Details for Client Code
- Blocking SOAP Web Services Requests
- SOAP Web Services Execution Log
- Distributing Integration Records
- Default Web Services Integrations Record
- Using Integration Records in Sandbox Accounts
- Token-based Authentication Credentials and Accounts
- Using Integration Records in Conjunction With SSO Calls
- Removing Integration Records
- Tracking Changes to Integration Records