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

Aberta
#587 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
javascript, openapi

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
JavaScript
Estrelas
1
Forks
1
Merge médio
3h 21min
PRs com merge (30d)
250

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de eizedev/pivotkit

Todas as issues de eizedev/pivotkit

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.