AGENT SKILL

0.2.2-understand-access_token_format_type

[0.2.2] Classification of the access_token internal structure: opaque (random string referencing server-side state) or

License 许可
MIT
最近更新
2026-10-09
Stars
★ 0
Forks
0

01 前言 Front Matter

name
0.2.2-understand-access_token_format_type
description
[0.2.2] Classification of the access_token internal structure: opaque (random string referencing server-side state) or

03 SKILL.md 正文

understand-access_token_format_type

CALL NUMBER: deep_oauth_2_0.access_token_format_type : oauth_2_0_and_openid_connect(10) DEFINITION: Classification of the access_token internal structure: opaque (random string referencing server-side state) or structured (JWT containing claims about scope, audience, expiration embedded directly).

Invoke this skill to understand access_token_format_type down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP/SWI-Prolog consistency gate): every reference below resolves.

THE RELATIVE ROOT (the import cone, by lib)

from ?

  • token_type (d3): OAuth 2.0 parameter indicating how the access_token is to be presented to the resource server, typically Bearer, specifying the authorization scheme to use in requests.

from deep_oauth_2_0

  • access_token_scope (d2): The specific permission set granted to the access_token; a space-delimited string drawn from the scopes requested and approved during authorization; determines what resources and actions the token authorizes.

from oauth_2_0_and_openid_connect

  • access_token (d1): OAuth 2.0 credential presented to the resource server; opaque to clients but contains or references authorization state; scoped and time-limited.
  • authorization_server (d2): OAuth 2.0 server that authenticates the resource owner, obtains consent, and issues access tokens and optionally refresh tokens and ID tokens.
  • bearer_token (d2): Token type defined in RFC 6750; any party possessing the token may use it; security relies on transport TLS and token secrecy.
  • expires_in (d2): Integer seconds indicating access token lifetime; returned alongside access_token in token response.
  • grant_type (d2): OAuth 2.0 parameter identifying which authorization flow is being used; values: authorization_code, client_credentials, refresh_token, password (deprecated).
  • introspection_endpoint (d2): RFC 7662 endpoint allowing resource servers to validate access tokens; returns active status, scope, expiry, and other token metadata.
  • refresh_token (d2): OAuth 2.0 credential used to obtain new access tokens without re-prompting the resource owner; long-lived and tied to the same scope as the original access token.
  • resource_indicator (d2): RFC 8707 parameter specifying the target resource server URI; server issues access token scoped to that specific resource, not just the general API.
  • resource_server (d2): Server hosting protected resources; validates incoming access tokens and returns resources only when tokens are valid and authorized.
  • token_endpoint (d2): OAuth 2.0 endpoint accepting authorization_code or other grants and returning access_token, refresh_token, and optional id_token.

Projected from the oauth 2 0 and openid connect KB (174 concepts / 97 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.

(leaf — this is an actual skill.)

04 同仓库更多 Skills