Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
zhaoxuya520/competition-oauth-oidc-chainAPI, SaaS e identità

competition-oauth-oidc-chain

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for OAuth, OIDC, redirect flows, state or nonce handling, PKCE, token exchange, refresh logic, claim mapping, and accepted login paths. Use when the user asks to trace redirects, callback parameters, scopes, state, nonce, P⁩

v2026.9.22-cab634b3 installazioni+3 in 7 giorni44,8K StelleMITsincronizzato 2 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-oauth-oidc-chain

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
beh65I9Eyk…Y1OVZrAg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettob31e05eb…9fbb33ad
b31e05eb081e…2d4e9fbb33ad3 file · ⁦2.1 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-oauth-oidc-chain@cab634b

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the hard part is proving how an OAuth or OIDC flow is shaped, exchanged, and ultimately accepted.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Map the auth chain in order: entry route, redirect, authorize request, callback, token exchange, refresh, and final accepting service.
  2. Record scopes, state, nonce, PKCE material, redirect URIs, and claim-bearing tokens before mutating anything.
  3. Separate token possession from actual identity acceptance.
  4. Keep browser-visible redirects and backend-visible token exchange in one compact chain.
  5. Reproduce the smallest redirect-to-acceptance flow that proves the decisive identity edge.

Workflow

1. Map The Redirect And Token Path

  • Record issuer, client ID, redirect URI, authorize parameters, callback parameters, token endpoint, and refresh path.
  • Note which values are user-controlled, derived, cached, or validated: state, nonce, PKCE verifier, audience, scope, or prompt.
  • Keep browser redirects, server-side exchanges, and resulting session state tied together.

2. Prove Token-To-Identity Acceptance

  • Show how code, ID token, access token, or refresh token turns into app session, claims mapping, tenant selection, or accepted privilege.
  • Record token claims, expiration, audience, subject, scopes, and the exact accepting app or backend edge.
  • Distinguish UI login success from backend authorization success.

3. Reduce To The Decisive OAuth Chain

  • Compress the result to the smallest sequence: entry request -> redirect -> callback -> token or claim acceptance -> resulting capability.
  • Keep one canonical good flow and one minimal mutated flow if a parameter change matters.
  • If the task broadens into generic web routing or storage behavior outside the auth chain, switch back to the broader web-runtime skill.

Read This Reference

  • Load references/oauth-oidc-chain.md for the redirect checklist, token checklist, and evidence packaging.
  • If the hard part is JWT header parsing, claim normalization, key lookup, or token validation confusion after issuance, prefer $competition-jwt-claim-confusion.

What To Preserve

  • Redirect URIs, parameters, codes, token claims, scopes, and the accepting service or callback
  • The exact point where claims or tokens become accepted app identity
  • One minimal replayable redirect-to-acceptance sequence

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.9.22-cab634b13 nov 2026cab634bb31e05ebFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login