Epic: v1.1 B2B organizations and enterprise SSO

Open
  • Is something wrong?
#389 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
5/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
authentication, authorization

Research direction

This is a milestone epic with no code paths named, so there is no file or test to start from. Do not begin implementation here; the issue says child tickets will be created when v1.1 becomes current. Done means every checklist item (invitations, verified domains, OIDC and SAML connections, home-realm discovery, self-service SSO setup) has its own scoped ticket that is closed.

Written by the indexing model from the issue text.

Description

easy epic P3 v1.1

Goal

What incumbents charge most for, free and in the open source product.

Scope

  • Organization invitations
  • Verified domains for organizations
  • Inbound enterprise OIDC connections per organization
  • Inbound enterprise SAML connections per organization (hardened library, signature-wrapping tests)
  • Home-realm discovery by email domain and just-in-time provisioning
  • Self-service SSO setup for an organization's own admin

Tickets are created when this milestone becomes current.

Dominant language
TypeScript
Stars
2
Forks
2
Avg merge
11h 40m
Merged PRs (30d)
104

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 fells-code/seamless-auth-api

All issues in fells-code/seamless-auth-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.