server: accept sign-in tokens from more than one OIDC issuer
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
- Domain
- authentication, backend-api-design
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
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 (
jwksUrior discovery). - A token exchange (
sources.<id>.http.auth.tokenExchange) goes to the token endpoint of the issuer that issued the subject token, not always toauth.issuer's. TodaytokenUrldefaults toauth.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.issuerkeeps 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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eizedev/pivotkit
-
accessibility area:react bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area:tests
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area:cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
area:cli enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:react enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in eizedev/pivotkit
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
mattabate/life-distributable#231 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sfbrigade/pocket-gardens#60 ·
Maintainers usually reply within 5 days
-
The print preview leaves writing space short by the margins of hidden headers, footers and solutionsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3329 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
devarshishimpi/codra#178 ·
Maintainers usually reply within 1 day