You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, manually configured webhooks from integrations did not have a secret attached to them. In order to improve security, we have deployed an update so that all new integrations will be created with a secret, and we are deprecating old integrations without a secret. You must migrate your integrations by January 31, 2024, when they will stop working.
We are contacting you because you have at least one integration that does not have a secret set. These integrations are:
https://readthedocs.org/dashboard/elyra/integrations/120634/
If you aren't using an integration, you can delete it. Otherwise, we recommend clicking on "Resync webhook" to generate a new secret, and then update the secret in your provider's settings as well. You can check our documentation for more information on how to do this.
Describe the issue
Received the following email:
Previously, manually configured webhooks from integrations did not have a secret attached to them. In order to improve security, we have deployed an update so that all new integrations will be created with a secret, and we are deprecating old integrations without a secret. You must migrate your integrations by January 31, 2024, when they will stop working.
We are contacting you because you have at least one integration that does not have a secret set. These integrations are:
https://readthedocs.org/dashboard/elyra/integrations/120634/
If you aren't using an integration, you can delete it. Otherwise, we recommend clicking on "Resync webhook" to generate a new secret, and then update the secret in your provider's settings as well. You can check our documentation for more information on how to do this.
You can read more information about this in our blog post: https://blog.readthedocs.com/security-update-on-incoming-webhooks/.
The text was updated successfully, but these errors were encountered: