Connecting an app to Time Trakkr has always used PKCE — the app proves it is the same one that started the sign-in, without holding a shared secret. That works for anything running in a browser or on your own machine, and it is what the Claude connector uses.
Some integrations cannot work that way. An app hosted by another vendor holds its credentials on their servers and authenticates with a client secret instead. Time Trakkr now accepts either — but never neither, and which one an app owes is fixed when it is registered rather than decided per request. An app registered for PKCE cannot skip it by leaving the challenge out.
Client secrets are not self-service. Anyone can still register a PKCE app automatically. A secret is issued out of band, by a person, because an open endpoint handing out secrets would let anyone opt themselves out of PKCE.
The approval screen now mentions Jira. A grant could already match Jira issues to your projects to pre-fill a timer; the screen did not say so. It does now. Nothing about what a grant reaches has changed — only the description, which should have named it from the start.
Refreshing a connection now re-checks the secret. Previously a refresh token alone was enough for its full thirty days. For apps that use a secret, the secret is checked every time.
Not yet built: disconnecting an integration from its side does not revoke the grant here. Until Time Trakkr has a revocation endpoint, take access back under Developer → Connected apps, which does end it immediately.