Refresh token loses original scopes during rotation #16
Replies: 2 comments 1 reply
|
Thanks for the detailed report and the log ids — you're right, this is a defect on our side, not your configuration. Refresh tokens were not persisting the scope granted at authorization, and since the refresh grant narrows the requested scope to the one stored in the refresh token, refreshed access tokens came out with empty We're shipping a fix that stores the granted scope in the refresh token and carries it through rotation. Refresh tokens issued before the fix don't carry it, so a fresh login will be needed once the fix is live. We'll update this thread when it's deployed. |
|
The fix is now live. Refresh tokens issued from now on store the scope granted at authorization, and refresh and rotation keep it: a refreshed access token carries the same scope and permissions as the original one (or the subset you request with scope, it can be narrowed, never widened). The token response now also returns the effective scope. A correction to my previous message about refresh tokens issued before the fix: they keep working if you pass scope explicitly on the refresh request, and the rotated refresh token you get back carries it from then on. Only a refresh of an old token without scope still comes back empty, since there is nothing stored to recover it from, in that case a new login fixes it. Thanks again for the precise report. |
Uh oh!
There was an error while loading. Please reload this page.
Hello I have a question,
Authorization Code issuance includes openid profile email mcp:invoke spike:run offline_access. Refresh returns the correct MCP audience but empty scope and permissions claims, both with the original scopes explicitly requested and with scope omitted.
Initial issuance: log_6ae47996d84b25f83f3ffd51
Refresh issuance: log_6ae479a3d84b25f83f3ffd57
The API has both permissions configured, access_token_authz, policy enforcement enabled, offline access enabled, and RBAC disabled. No custom Actions exist.
Please verify that original scopes are persisted in the refresh grant and recovered during refresh and rotation. Is this a known defect, and what is the supported fix?
All reactions