41 lines
1.0 KiB
Markdown
41 lines
1.0 KiB
Markdown
---
|
|
status: testing
|
|
phase: 13-virtual-local-cloud-operations
|
|
source: [13-VERIFICATION.md]
|
|
started: 2026-06-23T00:00:00Z
|
|
updated: 2026-06-23T00:00:00Z
|
|
---
|
|
|
|
## Current Test
|
|
|
|
number: 1
|
|
name: CONN-02 — Automatic provider OAuth token refresh during reconnect
|
|
expected: |
|
|
Triggering reconnect with an expired-but-refreshable OAuth token (no new_credentials
|
|
in POST body) calls the provider's refresh endpoint and stores a new access_token.
|
|
The test assertion is: decrypted credentials_enc after reconnect contains a new
|
|
access_token that differs from the original.
|
|
awaiting: user response
|
|
|
|
## Tests
|
|
|
|
### 1. CONN-02 — Automatic provider OAuth token refresh during reconnect
|
|
|
|
expected: |
|
|
Trigger reconnect via POST /api/cloud/connections/{id}/reconnect with an expired
|
|
(but still refreshable) OneDrive or Google Drive token. Inspect the decrypted
|
|
credentials_enc — expect a new access_token from the provider, not a re-encrypted
|
|
copy of the original.
|
|
result: [pending]
|
|
|
|
## Summary
|
|
|
|
total: 1
|
|
passed: 0
|
|
issues: 0
|
|
pending: 1
|
|
skipped: 0
|
|
blocked: 0
|
|
|
|
## Gaps
|