View source: R/methods__token.R
| revoke_token | R Documentation |
Attempts to revoke an access or refresh token when the provider exposes a revocation endpoint (RFC 7009).
Authentication mirrors the provider's token_auth_style (same as token
exchange and introspection).
Best-effort semantics:
If the provider does not expose a revocation endpoint, returns
supported = FALSE, revoked = NA, and status = "revocation_unsupported".
If the selected token value is missing, returns supported = TRUE,
revoked = NA, and status = "missing_token".
If the endpoint returns a 2xx, returns supported = TRUE, revoked = TRUE,
and status = "ok".
If the endpoint returns an HTTP error, returns supported = TRUE,
revoked = NA, and status = "http_<code>".
revoke_token(
oauth_client,
oauth_token,
which = c("refresh", "access"),
async = FALSE,
shiny_session = NULL
)
oauth_client |
OAuthClient object |
oauth_token |
OAuthToken object containing tokens to revoke |
which |
Which token to revoke: "refresh" (default) or "access" |
async |
Logical, default FALSE. If TRUE and an async backend is
configured, the operation is dispatched through shinyOAuth's async
promise path and this function returns a promise-compatible async result
that resolves to the result list. mirai is preferred when daemons are
configured via |
shiny_session |
Optional pre-captured Shiny session context (from
|
A list with fields:
supported: logical, TRUE when a revocation endpoint is configured.
revoked: logical or NA, TRUE when the provider accepted the
revocation request, NA when revocation could not be attempted or the
result is unknown.
status: machine-readable status such as "ok", "missing_token",
"revocation_unsupported", or "http_<code>".
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.