OpenID provider admin handlers, deactivation and plain delete
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication, backend
Research direction
Start by reading the OpenID provider admin-handler module and how the service mounts it behind its role layer; then trace the OIDC login flow and how External identities reference providers. Check the existing tests for those entry points, and run just ci. Done means the acceptance criteria hold for create, edit, deactivate/reactivate, and delete, with no handler-level auth checks and unique operation ids.
Written by the indexing model from the issue text.
Description
Parent
#41
What to build
The module provides admin handlers for OpenID providers, which the service mounts behind its own role layer.
- Create, edit, deactivate/reactivate, delete.
- The client secret is never returned, only overwritten.
- Identifying claim and issuer are frozen once an External identity references the provider.
- Deactivating blocks the provider's OIDC login and keeps everything; reactivating restores it.
- Plain delete is only allowed while no External identity references the provider.
Acceptance criteria
- No handler response contains the client secret; editing can overwrite it
- Changing the identifying claim or issuer of a referenced provider is refused
- A deactivated provider's OIDC login is refused; reactivating restores it with all External identities intact
- Plain delete of a referenced provider is refused; of an unreferenced one succeeds
- Handlers carry no auth checks of their own (the service's role layer guards them); operation ids are unique
-
just ciis green
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 10h 56m
- Merged PRs (30d)
- 34
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 myOmikron/code
-
wayfinder:task
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
myOmikron/code#102 · 2 comments ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 76/100
logto-io/logto#9837 · 1 comment ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
lingdojo/kana-dojo#32964 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Documentation status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mastra-ai/mastra#28194 · 1 comment ·
Maintainers usually reply within 1 day
-
priority-low refactor-3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days