Download sign-in with its own issuer (per-application issuers)
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
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript
- Domain
- authentication, backend-api-design
Research direction
Read the existing auth.issuer and output.downloads.signIn.issuer configuration and the issuer match check in related issue #434. Then map how identity binding handles issuer and subject pairs, and inspect how check-config reports authentication settings. The design needs to settle trusted issuer and shared subject namespace semantics before implementation; done means per-application download sign-in can be configured and checked while binding the same people safely.
Written by the indexing model from the issue text.
Description
Today the server accepts one auth.issuer, and output.downloads.signIn.issuer must equal it. Identity providers that give every application its own issuer (Authentik does this per OAuth provider) then force the download sign-in onto the MCP client's own provider. They also force REST and MCP into separate containers when they use different clients.
What works today: one issuer shared by MCP, REST and the download sign-in. That fits Entra ID, Keycloak realms and Auth0 tenants.
What I'd like:
output.downloads.signIncan name its own issuer and client.- The binding compares (issuer, subject) pairs across a configured list of trusted issuers that identify the same people.
- Possibly
auth.issuersas a list.
Things to decide in the design:
- How to state that two issuers share one subject namespace. Authentik's
subis per provider unless it is configured otherwise. - How check-config shows the setup.
Related: https://github.com/eizedev/pivotkit/issues/434 (issuer match check).
- 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