server: accept sign-in tokens from more than one OIDC issuer

Aperta
#587 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, openapi

Direzione di ricerca

Start with packages/pivotkit-server/src/options/http.js and read the existing auth.issuer and tokenUrl handling. First verify whether the identity provider supports RFC 8693 exchange with a subject token from another provider and whether PowerShell Universal passes the user's access token to a script; the issue says exchange routing depends on those findings. Done means supporting issuer-specific audiences, scopes and keys, routing exchanges to the issuing issuer, restricting which issuers each source may exchange, and preserving auth.issuer compatibility.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:server enhancement

pivotkit-server accepts sign-in tokens from one OIDC issuer (auth.issuer). Authentik gives each provider an issuer of its own by default. So a server that should accept tokens from two Authentik providers needs one of these today:

  • Authentik reconfigured to "issuer mode: global", with both providers signing with the same key;
  • or every client on one provider.

A typical case: PowerShell Universal passes on its user's token from its own provider, and Claude Code signs in through a second, public client.

Proposal: auth.issuers, a list of issuers.

  • Each issuer has its own audience, required scopes and key set (jwksUri or discovery).
  • A token exchange (sources.<id>.http.auth.tokenExchange) goes to the token endpoint of the issuer that issued the subject token, not always to auth.issuer's. Today tokenUrl defaults to auth.issuer's token endpoint (packages/pivotkit-server/src/options/http.js).
  • A source names the issuers whose tokens it may exchange. A token from another issuer is never passed on to that backend.
  • The docs recommend a pivotkit scope of its own per issuer (requiredScopes). If the audience is another application's client ID, every token issued to that application would otherwise be valid at pivotkit.
  • auth.issuer keeps working as the one-issuer form.

Before building it, check:

  • whether the identity provider accepts a token exchange (RFC 8693) with a subject token from another provider;
  • whether PowerShell Universal hands the signed-in user's access token to a script.

The design of the exchange routing depends on what that check shows.

Related: #441, a download sign-in with an issuer of its own.

Lingua principale
JavaScript
Stelle
1
Fork
1
Merge medio
3h 21m
PR unite (30g)
250

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di eizedev/pivotkit

Tutte le issue di eizedev/pivotkit

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.