Announcing Upcoming OAuth Improvements (1/19/21)
On January 26, 2021, we will release improvements to the process for performing OAuth authorization when distributing data to destinations that use OAuth authorization. We expect this change to decrease failed data deliveries to OAuth destinations and make managing OAuth authorizations much easier for you (especially if you have a large number of destination accounts for OAuth destinations).
Our previous process had several limitations, which this release addresses:
You were required to enter OAuth credentials every time you activated a new destination account.
We weren’t able to validate that the downstream platform account was compatible with the platform seat until we were ready to deliver data, which sometimes resulted in delivery issues.
There was no way for you to view and manage your OAuth connections at a high level.
New OAuth “Connections”
With this update, you will be able to create an OAuth “connection” for a particular OAuth destination and reuse that connection for multiple destination accounts. These OAuth connections can now be viewed and managed on a new OAuth Connections page in Connect.
From this page, you can view and manage all of your OAuth connections, as well as view the destination accounts that use each connection.
Improved Destination Account Validation
When you activate a destination account for an OAuth destination, you will validate the OAuth connection with your seat ID before the destination account can be activated, which will decrease OAuth authorization-related distribution issues.
And when you edit a destination account for an OAuth destination, the OAuth connection must be re-validated to ensure that the distributions continue to be made successfully.
Note
As before, the OAuth authorization must be performed by a user with the appropriate permission level at the end platform.
Note
In the coming months, you will be asked to migrate your OAuth destination accounts to this improved workflow to ensure you are benefiting from the improved process.
Note
Distribution API users:
For users of v1.0 of the Distribution API, this change will not affect your current OAuth workflows.
For users of v2.0 of the Distribution API, you are already benefiting from this update, so no action is required.