swicg/general

Advancing Ticket Auth to more interoperable implementations

Open

#35 opened on Oct 9, 2023

View on GitHub
 (10 comments) (3 reactions) (0 assignees) (4 forks)github user discovery
agenda-itemhelp wanted

Repository metrics

Stars
 (51 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

@dshanske and I are going to be working on TicketAuth implementations. From the draft specification:

Ticket Auth is an extension to IndieAuth that enables a publisher to send authorization, known as a ticket, that can be redeemed for an access token. This allows both solicited and unsolicited invitations to fetch restricted resources.

If anyone is interested in independently implementing the spec along with us, please respond here!

Contributor guide

Research direction
Read the TicketAuth specification and examine existing IndieAuth implementations to understand the authentication flow.
Tech stack
None
Domain
authentication
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitIndieAuth
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60