ably_auth_openapi/models/
token_revocation_request.rs

1/*
2 * Ably Platform Auth REST API
3 *
4 * The subset of the Ably **platform** REST API used for authentication and token lifecycle: requesting Ably Tokens, revoking them, and reading server time. This is a *separate* API from the Ably Chat REST API (`openapi/ably-chat-rest.yaml`, path prefix `/chat/v4`) — token issuance and revocation live on the platform host under `/keys/...`, not under `/chat/_*`.  ## Scope & provenance Ably publishes an authoritative platform spec, [`ably/open-specs`](https://github.com/ably/open-specs) `platform-v1.yaml`, which covers the full generic pub/sub REST API (`/channels`, `/push`, `/keys`, `/stats`, `/time`). **This document is deliberately narrow**: it models only the endpoints this project's authentication story ([ADR-0012](../docs/adr/0012-token-issuance-permissions.md), [SPEC §13](../docs/SPEC.md)) touches — `POST /keys/{keyName}/requestToken`, `POST /keys/{keyName}/revokeTokens`, and `GET /time`. Field-level details are cross-checked against `platform-v1.yaml`, the Ably auth docs, and the `ably-js` auth implementation (see [`../docs/research/2026-07-24-ably-chat-auth-permissions.md`](../docs/research/2026-07-24-ably-chat-auth-permissions.md)).  ## Relationship to the Chat client `ably-chat-rs` is a Chat REST client; it does not itself sign TokenRequests or call `/keys/...` (ADR-0012 Tier 4). This spec documents the platform endpoints a *token server* (or the official `ably` crate) uses to mint the Bearer credentials that are then handed to the Chat client. Capability documents carried by these tokens are described in SPEC §13, not here. 
5 *
6 * The version of the OpenAPI document: 1.0.0
7 * 
8 * Generated by: https://openapi-generator.tech
9 */
10
11use crate::models;
12use serde::{Deserialize, Serialize};
13
14/// TokenRevocationRequest : A request to revoke previously-issued tokens.
15#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
16pub struct TokenRevocationRequest {
17    /// Up to 100 target specifiers, each a `type:value` string where `type` is `clientId`, `revocationKey`, or `channel`. 
18    #[serde(rename = "targets")]
19    pub targets: Vec<String>,
20    /// Only tokens issued before this timestamp (epoch milliseconds) are revoked. Defaults to the current time when omitted. 
21    #[serde(rename = "issuedBefore", skip_serializing_if = "Option::is_none")]
22    pub issued_before: Option<i64>,
23    /// When true, enforcement is postponed ~30 seconds and live connections are hinted to obtain a fresh token, avoiding an abrupt disconnect. 
24    #[serde(rename = "allowReauthMargin", skip_serializing_if = "Option::is_none")]
25    pub allow_reauth_margin: Option<bool>,
26}
27
28impl TokenRevocationRequest {
29    /// A request to revoke previously-issued tokens.
30    pub fn new(targets: Vec<String>) -> TokenRevocationRequest {
31        TokenRevocationRequest {
32            targets,
33            issued_before: None,
34            allow_reauth_margin: None,
35        }
36    }
37}
38
ably_auth_openapi/models/token_revocation_request.rs

ably_auth_openapi/models/
token_revocation_request.rs
