Token request auth editor form

[filipeforattini]

Parent

Spec #217

What to build

The Token request auth editor form. In the auth editor, selecting the Token request method shows: a picker for the login request and the optional refresh request (requests of the same collection), extraction path fields for access/refresh token, the expiry source currently in effect (auto-detected layer) with the ability to override (response field / manual TTL), the secret name fields (defaults prefilled), and current token status (valid/expired, when it expires). The form works at request, folder, and collection scope through the scope config page.

Acceptance criteria

• The auth editor offers the Token request method with login/refresh request pickers scoped to the collection
• Extraction paths and secret names are editable with defaults prefilled; dotted secret names accepted
• The expiry source in use is displayed and can be overridden to a response field or manual TTL
• Current token status (valid/expired and expiry time) is visible
• The form functions at request scope and inside the scope config page for folder/collection
• Component tests cover method selection, field persistence, and status display

Blocked by

• Token request renewal robustness: 401 retry, refresh request, guards #224