mirror of
https://github.com/Drop-OSS/drop.git
synced 2026-07-25 04:15:36 -04:00
[PR #28] [MERGED] overhaul auth and futureproof it with argon2 #178
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Drop-OSS/drop/pull/28
Author: @Huskydog9988
Created: 3/22/2025
Status: ✅ Merged
Merged: 3/23/2025
Merged by: @DecDuck
Base:
develop← Head:auth-overhaul📝 Commits (10+)
6ed7e76move auth pages into auth dire08a13fadd sharp for ipx2027c69fix signout2c9fdebnew accounts use argon2257cdacmake signup less error prone in dbc1272dcuse arktype for clientside validation690aa04switch back to jsonf9e6702Merge branch 'develop' into auth-overhaul1f30960address some issues5704289move register to auth path📊 Changes
17 files changed (+381 additions, -133 deletions)
View changed files
📝
.vscode/settings.json(+19 -16)📝
README.md(+5 -3)📝
components/UserHeader/UserWidget.vue(+1 -1)📝
error.vue(+1 -1)📝
middleware/require-user.global.ts(+5 -2)📝
package.json(+3 -0)📝
pages/auth/register.vue(+14 -7)📝
pages/auth/signin.vue(+0 -0)📝
pages/auth/signout.vue(+2 -2)📝
server/api/v1/auth/signin/simple.post.ts(+53 -16)📝
server/api/v1/auth/signup/simple.post.ts(+55 -72)📝
server/internal/security/simple.ts(+18 -7)📝
server/plugins/redirect.ts(+1 -1)📝
server/routes/signout.get.ts(+1 -1)📝
server/tsconfig.json(+4 -1)📝
tsconfig.json(+4 -1)📝
yarn.lock(+195 -2)📄 Description
Main item of concern rn for me is if the credentials field on LinkedAuthMec should remain. Removing it would require a more complex migration strategy, but we could also just drop it and tell people to re-setup the server. If the later route is used, a few options open up, such as trimming down the number of migrations (iirc you should only generate these before a release), plus it would make the publisher and developer to company metadata source much easier.
If the later option is not chosen, getting a reset password screen down should be moved up on the timetable so users can be moved to argon2 when they signin.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.