Module tokens 

Synapse admin API: registration-token endpoints.

Re-exports

use std::time::Duration; 🔒

use ruma::MilliSecondsSinceUnixEpoch; 🔒

use ruma::UInt; 🔒

use ruma::uint; 🔒

use synapse_admin_api::registration_tokens::RegistrationToken; 🔒

use tuwunel_core::Result; 🔒

use tuwunel_core::utils::time::timepoint_from_epoch; 🔒

use tuwunel_service::registration_tokens::DatabaseTokenInfo; 🔒

use tuwunel_service::registration_tokens::TokenExpires; 🔒

use tuwunel_service::registration_tokens::TokenInfo; 🔒

pub(crate) use self::create::admin_create_token_route; 🔒

pub(crate) use self::delete::admin_delete_token_route; 🔒

pub(crate) use self::get::admin_get_token_route; 🔒

pub(crate) use self::list::admin_list_tokens_route; 🔒

pub(crate) use self::update::admin_update_token_route; 🔒

Modules

create 🔒

delete 🔒

get 🔒

list 🔒

update 🔒

Functions

database_token_response 🔒

Map a token and its stored metadata into the admin API wire shape. pending is always zero: tuwunel consumes uses in a single step with no two-phase registration model.

token_expires 🔒

token_response 🔒

Map a validated token into the admin API wire shape. Config-file tokens carry no usage state, so they read as unlimited, never expiring, and unused.