dependabot[bot] e89b4c64c8 Bump follow-redirects from 1.15.4 to 1.15.6
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.4 to 1.15.6.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](https://github.com/follow-redirects/follow-redirects/compare/v1.15.4...v1.15.6)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
2024-03-16 22:45:47 +00:00
2024-01-10 03:30:47 +01:00
2024-01-10 01:35:12 +01:00
2024-01-10 01:45:32 +01:00
2024-01-11 14:20:55 +01:00
2024-01-14 05:34:58 +01:00
2024-01-10 02:12:02 +01:00

Osu Oauth Middleware Server hosted on Vercel

Route access token back to end user without them needing own Api credentials!

How to use:

  1. Fork Repo
  2. Deploy on Vercel
  3. Create Api Client use the Vercel Domain as Callback
  4. add Envoirment variables
  • SCOPE: scopes
  • CALLBACK_URL: localy hosted endpoint to where the access_token should be send to
  • URL: vercel Domain
  • PORT: Vercel server Port / default is 9000
  • CLIENT_ID: client_id
  • CLIENT_SECRET: client_secret
  1. Add link to the vercel domain with port as state to /authorize: https://example.vercel.app/authorize?port=4200

  2. recieive anser at: https://localhost:4200/{CALLBACK_URL}?access_token={access_token}&refresh_token={refresh_token}&expires_in={expires_in}

  3. profit?

To resfresh the token request this POST: https://example.vercel.app/refresh?port=4200 body: refresh_token : {refreshtoken}

new token should be send like in 6

use at own risk, security holes might be in there

Description
No description provided
Readme MIT 128 KiB
Languages
JavaScript 91.5%
HTML 8.5%