Skip to content

Conversation

@pan93412
Copy link
Member

  • refactor: remove unused parameters
  • refactor: save OAuth Token in plaintext
  • chore: clean up dependencies
  • chore: update dependencies
  • style: reformat code
  • fix: runtime bugs

Saving the token in plaintext may be unsafe, but it allows for usable impersonation.

The RFC Draft "OAuth 2.0 for Browser-Based Applications" [^1] does not require the token to be encrypted.

This approach may slightly reduce the CPU time for an edge request, but the difference should not be very noticeable.

[^1]: https://datatracker.ietf.org/doc/html/draft-ietf-oauth-browser-based-apps#section-6.1.3.2
@pan93412 pan93412 self-assigned this Sep 15, 2025
@vercel
Copy link

vercel bot commented Sep 15, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
admin-frontend Ready Ready Preview Comment Sep 15, 2025 3:32am

@linear
Copy link

linear bot commented Sep 15, 2025

@pan93412 pan93412 force-pushed the pan93412/dbp-29-dont-encrypt-cookie branch from 351c2a9 to 961a9a8 Compare September 15, 2025 03:30
@pan93412 pan93412 merged commit 6e141cc into main Sep 15, 2025
3 checks passed
@pan93412 pan93412 deleted the pan93412/dbp-29-dont-encrypt-cookie branch September 15, 2025 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants