Epic: v1.2 SCIM and attack protection

Open
#390 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
Tech stack
react, typescript

Research direction

This is a v1.2 epic that lists four large workstreams (SCIM 2.0 server, cross-account velocity detection, pluggable CAPTCHA, i18n) and says tickets will be created later. There is no single file, test or entry point to start from; begin by reading the repository's existing authentication routes and the milestone discussion. Done means the child tickets exist and each has its own acceptance criteria.

Written by the indexing model from the issue text.

Description

epic P3 secure v1.2

Goal

Provisioning and defenses that larger organizations expect.

Scope

  • SCIM 2.0 server for Users and Groups (RFC 7643, 7644), validated with the Okta and Entra validators
  • Cross-account velocity detection for credential stuffing
  • Pluggable CAPTCHA (Turnstile, hCaptcha)
  • i18n for the hosted pages and the React UI

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.