chore(deps): consolidate JWT handling on jose

Open
#439 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
node.js, typescript

Research direction

Start by locating the internal service token verification and the uses of base64url, jose, and jsonwebtoken. Check how the existing verification works before moving it to jose and replacing the encoding with Node's native base64url support. Done means internal service tokens use jose and both jsonwebtoken and base64url are removed.

Written by the indexing model from the issue text.

Description

P3 secure v1.0

Why

The API carries two JWT stacks (jose and jsonwebtoken) and the unmaintained base64url. Each is a surface to keep safe.

What

  • Move internal service token verification to jose
  • Replace base64url with Node's native base64url encoding
  • Remove both dependencies
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.