[M8.1] SSO OIDC

Open
  • Is something wrong?
#236 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
authentication, backend-api-design

Research direction

Start with dependency M2.2 and trace the control plane and web UI authentication entry points. The issue gives no file or test names, so locate the existing sign-in and organization settings flows before planning the OIDC work. Done means all four providers sign in on test tenants, just-in-time provisioning assigns the default role, and enforce-SSO blocks password sign-in for that organization.

Written by the indexing model from the issue text.

Description

blocked priority:P2 security-review task track:control-plane track:web
Task id

M8.1

Track

C: control plane, W: web UI

Scope
  • Org-level OIDC (Google, GitHub, Microsoft Entra, Keycloak tested), JIT provisioning with default role, enforce-SSO option.
Acceptance criteria

Each provider signs in on a test tenant; enforce-SSO refuses password sign-in for that organization.

Depends on

M2.2

Blocked by

Owner: test tenants or client credentials at the providers.

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

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 shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.