identity/com.midnight.kuira.core.identity.backup/DriveAuthManager

DriveAuthManager

Obtains authorization for the Drive appDataFolder scope via Play Services AuthorizationClient. This is separate from the passkey/Credential-Manager flow but resolves to the same Google account the user picks at consent.

Inheritors

PlayServicesDriveAuthManager

Functions

authorize

abstract suspend fun authorize(): AuthorizeOutcome

Request the drive.appdata scope. Returns AuthorizeOutcome.Authorized when consent already exists (silent), or AuthorizeOutcome.NeedsConsent carrying an IntentSender the UI must launch.

revoke

abstract suspend fun revoke()

Revoke the Drive appDataFolder grant (#246 — true backup disable). After this the app no longer has Drive access; the next authorize returns AuthorizeOutcome.NeedsConsent. No-op if nothing is currently granted. Best-effort: a network failure to reach the revoke endpoint is logged, not thrown (the local grant is gone from the user's intent either way).

silentTokenOrThrow

suspend fun DriveAuthManager.silentTokenOrThrow(): String

Returns a drive.appdata access token without UI, or throws if consent has not been granted yet. Use from headless paths (e.g. the dust backup coordinator during a routine refresh) — the first-time consent must come from a UI flow (DriveAuthManager.authorize + launching the IntentSender).

tokenFromConsent

abstract fun tokenFromConsent(data: Intent?): DriveAuth

Extract the token from the consent activity result Intent.