Currently the client secret and the organization secrets are a long lasting tokens.

The problem at the moment is that if they leak at any way, a support ticket is needed in order to invalidate those tokens.

This idea proposes a button below each of the long living secrets (and an API call) that revokes the current secret and generates a new one. With this change long lasting secrets will still work. However who wants to will be able to use short lived secrets by automating secrets rotation. And incidents related to secrets leak will be easier to contain.