jargonsdev/jargons.dev

Auth Feature - Fourth Iteration

Open

#30 opened on Apr 4, 2024

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)MDX (45 forks)auto 404
:arrow_upper_right: medium priority:sparkles: enhancementhacktoberfest

Repository metrics

Stars
 (54 stars)
PR merge metrics
 (PR metrics pending)

Description

The third iteration of the auth feature should focus on enhancing the OAuth flow and adding a signout/disconnect feature.

This is a follow up to the initial iterations...

Tasks

  1. Store OAuth Flow State Object in Cookies: Implement the todo that suggests storing the OAuth flow state object to cookies. This stored state should be compared with the state param returned from the GitHub OAuth flow in the github/oauth/callback handler to prevent CSRF attacks.

Related Files

  • github/oauth/callback.js
  • lib/actions/do-auth.js

Acceptance Criteria

  • OAuth flow state object is stored in cookies and compared with the state param.
  • Signout/disconnect feature is implemented and accessible through the doAuth action

Additional Notes

  • Nothing much... just ask a question or share ideas, if you've got any 😉

Contributor guide

Research direction
Understand the current OAuth flow in github/oauth/callback.js and lib/actions/do auth.js. Implement storing the OAuth state object in cookies when initiating the flow, and verify it against the state parameter returned in the callback to prevent CSRF. Additionally, implement a signout/disconnect feature in the doAuth action.
Tech stack
javascriptnodejs
Domain
backendauthentication
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60