Problem Statement:

Client secret regeneration events for the knowledge base widget and AI chatbot are not currently captured in Team Auditing. When a widget stops authenticating unexpectedly and no team member recalls making a change, there is no audit trail to identify who regenerated the secret or when the change was made. This gap was acknowledged in the KB as a known limitation. For security-critical actions that immediately impact all JWT-enabled integrations across a project, the absence of an audit record creates significant operational and compliance risk.

Suggested Enhancement:

Extend the existing Team Auditing system to capture client secret regeneration events for the knowledge base widget and AI chatbot, consistent with the audit logging already in place for JWT SSO configuration changes (which logs primary and secondary token regeneration events). Each log entry should record the action type, timestamp, the identity of the administrator who performed the action, and the widget or chatbot affected.

Customer Benefit:

Administrators can quickly identify the source and timing of authentication failures caused by unannounced secret regeneration. Teams operating in regulated environments gain the audit trail needed to meet access control and change management requirements. Reduces mean time to resolution for JWT authentication incidents.