Is Digital Source Tracker affected by the deprecation of Consumer Secrets in change sets and packages?
DST is not affected by the deprecation of Consumer Secrets in change sets and packages.
In July 2022, Salesforce announced that the Consumer Secret field on the Auth. Provider will contain a dummy value if the Auth. Provider is deployed via change sets or packages. The customer is then responsible for manually modifying the Consumer Secret after deployment/installation. Although DST relies on using the Consumer Secret field in the Auth. Provider for authentication with Google Analytics, the Auth. Provider is created and configured manually by the customer after installing the DST package. However, customers cannot set up the Auth. Provider in a sandbox and then use a change set to deploy it to production. The Auth. Provider must be configured manually in the production org.
Comments
0 comments
Please sign in to leave a comment.