Epic: v0.23 roles, permissions and hooks

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

Research direction

This is a tracking epic whose scope lists permissions, organization roles in tokens, adapter guards, custom claims, signed webhooks, login hooks and SIEM streaming, with children linked as sub-issues but not named here. Do not start on the epic itself; open its sub-issues and pick one that names a file or entry point. Done means the child issue's own acceptance criteria are met.

Written by the indexing model from the issue text.

Description

easy epic P2 v0.23

Goal

Apps can authorize on what Seamless Auth issues, and extend it without forking: permissions and organization roles in the token, a guard for them in every adapter, custom claims, signed webhooks, login hooks, and audit streaming to a SIEM.

v0.23 also finishes v0.21 before new features land. The API version v0.22.0 went to the OpenID Provider session binding change, so this roadmap release is named v0.23.

Order

  1. Security review follow-ups (#558). Fixes to code that is already shipped, across the API, the provider edge and every adapter. These come first.
  2. Finish v0.21: native and desktop apps on the OpenID Provider (#551, including the admin API ADR #544 and CLI sign-in fells-code/seamless-cli#316), the open provider bugs, OpenID certification (#412), the provider guides (fells-code/seamless-auth-docs#114) and the live Entra ID check (fells-code/seamless-cli#302).
  3. Permissions and organization roles: #415, #416, then schemas, guards in every adapter, console, client SDK and provider claims.
  4. Extensibility: custom claims (#417), webhooks (#418), login hooks (#419), SIEM streaming (#420), with their schemas, console pages, CLI and Node verification helper.
  5. Docs, templates and release (#561).

Done when

Every sub-issue is closed or moved with a reason, each feature has a published guide a coding agent can follow, the starter templates show a permission check, and the release is announced.

Children are linked as sub-issues. #551 and #558 are epics with their own sub-issues.

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.