Skip to content

fix: refresh user token on public iam client - #16

Merged
phil-accelbyte merged 1 commit into
mainfrom
fix/public-iam-token-refresh
Jun 23, 2026
Merged

phil-accelbyte merged 1 commit into
mainfrom
fix/public-iam-token-refresh

Conversation

@phil-accelbyte

Copy link
Copy Markdown
Collaborator

Problem

For public IAM clients (no client secret), the refresh-token request sent client_id in the form body instead of via HTTP Basic auth. The token endpoint rejected this, so token refresh failed for authorization-code (browser-login) profiles — users were forced to re-login once their access token expired.

Fix

Always send Basic auth on refresh — client_id:client_secret for confidential clients, client_id: (empty secret) for public clients — and drop the form-body client_id.

Tests

  • Public-client refresh sends Basic auth with an empty secret and does not duplicate client_id in the form body.

Public IAM clients (no secret) sent client_id in the refresh form body
rather than via Basic auth, which the token endpoint rejected — breaking
token refresh for authorization-code profiles. Always send Basic auth
(client_id with an empty secret for public clients) and drop the form-body
client_id.
@phil-accelbyte
phil-accelbyte merged commit 9d1eb35 into main Jun 23, 2026
5 checks passed
@phil-accelbyte
phil-accelbyte deleted the fix/public-iam-token-refresh branch June 23, 2026 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant