pub type TokenResponse = TokenRequest;Expand description
Output of the token-mint pipeline — the (possibly mutated)
TokenRequest ready to be folded back into the canonical
JwtClaims and signed.
Aliased Type§
pub struct TokenResponse {
pub username: String,
pub app_ids: Vec<String>,
pub extra: Map<String, Value>,
}Fields§
§username: StringJWT subject (typically the username / email).
app_ids: Vec<String>App ids this token grants access to. Plugins may inspect this to make per-app decisions.
extra: Map<String, Value>Mutable claim accumulator. Plugins read existing claims here
and mutate to attach their own. Yeti-canonical claims (sub,
exp, apps, etc.) are populated by the host before the
pipeline runs and after it finishes; plugins should treat
them as read-only inputs and write to keys they own.