メニュー
How to use @t4h.framework/oidc OIDCAuthorization, context fields, and the authorize module discovery plus client-credentials and introspection. Use when configuring OIDC authorization or imports from @t4h.framework/oidc.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Documents @t4h.framework/amber (Amber client, Ticket operations, HTTP activities, Basic auth, runtime-claims peers). Use when implementing ticket or protocol flows—integration, creation, updates, transfers, tabulation, comments, locks—or when the user asks about ticket/protocol integration, creating tickets or protocols, or similar; also when they mention @t4h.framework/amber or Amber channel APIs.
Guides assembling T4H apps with Workflow definitions, default-export App wiring, and routing to the correct framework-* skill per @t4h.framework package. Use when scaffolding workflows, structuring main plus src/workflows, nesting startWorkflow, or choosing which package skill to read for HTTP, auth, ORM, Amber, cache, FS, SFTP, or SMTP.
How to use @t4h.framework/cache CacheClaim get/set, TTL, and Serializable values; pairing with @t4h.framework/http OAuth2. Use when implementing caches or imports from @t4h.framework/cache.
How to use @t4h.framework/core App, Workflow, Authorization, Env, Claim, History, Binary, Serializable, startWorkflow, StartWorkflowActivity, WorkflowClaim, and WorkflowRef. Use when building T4H apps, workflows, nested workflow starts, or importing from @t4h.framework/core.
How to use @t4h.framework/fs FileSystemClaim read/write and Binary. Use when handling filesystem claims or imports from @t4h.framework/fs.
How to use @t4h.framework/http HttpClient, http singleton, HttpRequestActivityInput, HttpAuth, OAuth2, HttpClientRequestClaim. Use when calling HTTP from workflows or extending OAuth2.
| name | t4h-framework-oidc |
| description | How to use @t4h.framework/oidc OIDCAuthorization, context fields, and the authorize module discovery plus client-credentials and introspection. Use when configuring OIDC authorization or imports from @t4h.framework/oidc. |
OIDCAuthorization extends Authorization. toManifest() sets pathToModule to @t4h.framework/oidc/authorize and passes OIDCAuthorizationContext.
Peer dependency: @t4h.framework/core.
OIDCAuthorization, OIDCAuthorizationContext, manifest types.@t4h.framework/oidc/authorize: default oidc(context) in oidc-authorize.ts.OIDCAuthorizationContext| Field | Purpose |
|---|---|
discoveryUrl | OpenID discovery document URL (GET). JSON must include token_endpoint and introspection_endpoint. |
clientId, clientSecret | grant_type: client_credentials at token_endpoint. |
token | Caller credential; expect Bearer …. Only the part after Bearer is sent as the introspection token. |
scope | Optional string[] → joined with spaces for the token POST. |
resource | Optional; added to the client-credentials body when set. |
oidc-authorizediscoveryUrl → read token_endpoint, introspection_endpoint (errors throw on non-OK).token_endpoint, application/x-www-form-urlencoded: grant_type, client_id, client_secret, optional scope, resource → read access_token from JSON.introspection_endpoint, application/json: body { token } where token is getAccessToken(context.token) (substring after Bearer ). Header Authorization: Bearer <access_token from step 2> (client-credentials token).true iff introspection JSON has active: true; else false. Non-OK HTTP throws.If token does not start with Bearer , the introspection body sends null for token.