You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d01c427
Browse filesBrowse the repository at this point in the historyBrowse files
authored
feat(cloud-connection): unbind keeps an identity residual for re-bind continuity (#1797)
* feat(cloud-connection): unbind keeps an identity residual for re-bind continuity
Disconnect clears the credential (revoking cloud-side first) but keeps
{runtimeId} in the store — a later re-bind to the same org claims and
revives the same registration (cloud claim rule reactivates the revoked
row) instead of minting a new device per disconnect cycle. Same shape
as an iCloud device record surviving sign-out.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* test: unbind expectation matches the identity-residual behavior
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Unbind keeps an identity residual: the credential is cleared (and revoked cloud-side first) but `runtimeId` survives in the store, so a later re-bind to the same org claims — and revives — the same registration instead of minting a new device per disconnect cycle. `ConnectionCredentialStore.read()` accepts token-less residual records.
0 commit comments