member badge
Arunkumar Kumaresan
All JWT-enabled widgets in a project share a single client secret. Regenerating the secret from any one widget applies the change to every other JWT-enabled widget in the project immediately, with no option to limit the scope to a single widget. Teams that maintain separate production and test widgets within the same project cannot make JWT credential changes in their test widget without affecting their live widget.
Workaround Limitations:
  1. There is no way to regenerate the client secret for a single widget; the change always applies to all JWT-enabled widgets in the project.
  2. Administrators have no visibility in Team Auditing into when or by whom the client secret was last regenerated.
Requested Solution: Support independent JWT configurations per widget, so each widget can hold its own client secret. Specifically:
  1. Each widget should be able to generate and store its own client secret, independent of other widgets in the project.
  2. Regenerating the secret on one widget should have no effect on any other widget in the same project.
  3. The existing shared configuration should remain the default, with per-widget configuration available as an opt-in.
Benefits:
  1. Teams can test JWT credential changes on a non-production widget without affecting live widgets.
  2. Accidental secret regeneration on one widget does not take down all other JWT-authenticated widgets in the project.
  3. Projects with multiple JWT-authenticated widgets can rotate credentials independently.
Use Cases: Production and test widget isolation within the same project, multi-team widget ownership with independent credential management, staged credential rotation without coordinated deployments.