Epic: v2.0 workforce identity

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

Research direction

This is a tracking epic, not a task: the checklist lists seven workstreams (SAML 2.0 identity provider, groups and app launcher, outbound SCIM, directory sync with Google Workspace and Entra ID, lifecycle handling, a Terraform provider, and high availability guidance), and the body says individual tickets will be created when the milestone becomes current. Nothing here names a file, test or entry point, so a newcomer should wait for a child ticket or ask the maintainers which workstream is open to help with.

Written by the indexing model from the issue text.

Description

easy epic P4 v2.0

Goal

Run an organization's own staff identity on Seamless Auth.

Scope

  • SAML 2.0 identity provider
  • Groups, application assignment and an app launcher
  • Outbound SCIM to apps
  • Directory sync with Google Workspace and Entra ID
  • Lifecycle: joiner, mover, leaver, inactive accounts
  • Terraform provider
  • High availability guidance

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.