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

Open
#587 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, openapi

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
3h 21m
Merged PRs (30d)
250

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eizedev/pivotkit

All issues in eizedev/pivotkit

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.