Epic: v2.1 strong authentication everywhere

Open
  • Is something wrong?
#392 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
nginx, typescript
Domain
authentication

Research direction

This is an epic: a checklist of six v2.1 workstreams, with tickets to be created later when the milestone becomes current. There is no single file, test or entry point to start from. Pick a checklist item and wait for its child ticket before reading code; the epic itself has no defined done state.

Written by the indexing model from the issue text.

Description

epic P4 secure v2.1

Goal

Phishing-resistant sign-in in front of every app, including ones that know nothing about Seamless Auth.

Scope

  • Forward-auth for reverse proxies (Caddy, Traefik, nginx)
  • Per-application authentication policy
  • RADIUS and LDAP front ends for VPNs and legacy apps
  • Registered-device inventory
  • Shared Signals (CAEP, RISC) transmitter and receiver
  • DPoP, PAR and token exchange, opt-in per client

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.