feat(sync): add Microsoft account connect CLI
nocal account connect microsoft runs the PKCE browser flow, reads /me, upserts the deterministic account row, and persists tokens to Secret Service as the final connected-state gate. Account IDs are hashed from the remote subject so reconnect is idempotent, and a secret-store failure leaves the same coherent state as a disconnect. Ships a placeholder client ID with NOCAL_MICROSOFT_CLIENT_ID override until a real Entra registration exists.
This commit is contained in:
10
README.md
10
README.md
@@ -182,6 +182,10 @@ them; omission is not mislabeled as a remote deletion tombstone. This avoids
|
||||
beta and undocumented delta routes, at the cost of refetching each secondary
|
||||
window instead of incrementally updating it.
|
||||
|
||||
There is still no account UI/CLI orchestration or live Microsoft credential
|
||||
integration, and remote writes remain out of scope. Account setup and
|
||||
orchestration are next.
|
||||
Account setup begins with `nocal account connect microsoft`: it runs the
|
||||
PKCE browser flow, reads `/me`, upserts the deterministic account row, and
|
||||
stores the tokens in the Secret Service keyring as the final connected-state
|
||||
gate. This build ships a placeholder client ID; live connect requires a real
|
||||
mobile/desktop Entra registration supplied via `NOCAL_MICROSOFT_CLIENT_ID`.
|
||||
There is still no account TUI or sync orchestration, and remote writes remain
|
||||
out of scope.
|
||||
|
||||
Reference in New Issue
Block a user