In the event that your app’s client secret has been compromised, you should immediately rotate it. Smile makes it possible for your app to rotate it’s client secret with zero downtime.
After generating the new secret, both the old and new client secrets can be used to acquire access tokens. Update your app to use the new client secret.
Step 3: Use the new client secret to verify webhooks
Webhooks are always signed with the primary client secret. Once the old secret is revoked, the new secret will automatically be promoted to primary status. Configure your application to accept webhooks signed with either the old or the new client secret.
Click Revoke next to the old client secret. This will remove it and promote the new secret to be your primary client secret. Any access tokens that were generated using the old revoked client secret will still be valid until they expire.