supabase / auth / 33076969398

71%

push

github

feat(oauth): emit login metering events for OAuth server token exchanges (#2749)

## What kind of change does this PR introduce?

Feature (analytics/observability only, no behavior change)

## What is the current behavior?

OAuth 2.1 authorization server logins aren't represented in standard
`Login` metering events:
- The initial authorization_code → token exchange emits no login event.
- Refreshes of OAuth server tokens only emit the generic `login_method:
token` event, with no attribution to the OAuth server or client.

This makes it impossible to answer "what share of logins flow through
the OAuth server?"

## What is the new behavior?

- `handleAuthorizationCodeGrant` now records a
`oauth_server_authorization_code` login event (with `client_id`) once
the exchange has fully succeeded.
- `RefreshTokenGrant` now additionally records an
`oauth_server_token_refresh` login event (with `client_id`) for OAuth
server sessions, alongside the existing (unchanged) generic `token`
event.
- `metering.LoginData` gained a `ClientID` field, surfaced as
`client_id` in the emitted log fields.

 

 Resolves AUTH-1539

---------

Co-authored-by: fadymak <dev@fadymak.com>

22 of 22 new or added lines in 3 files covered. (100.0%)

15974 of 22497 relevant lines covered (71.01%)

485.06 hits per line