[example issue] refactor auth logic #2
Labels
No labels
CI/CD
MongoDB
PostgreSQL
api
authentication
bug
documentation
duplicate
enhancement
example issue
fix
good first issue
help wanted
high-level requirement
infrastructure
invalid
low-level requirement
medium-level requirement
question
security
test
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AndreFerreira5/starranja#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
this is a template issue for you to follow
the authentication logic works right now, but it was written in a rush to get everything ready for production. now that we have more free time and the boss is less angry, we should refactor it and make it more robust, modular and secure. also, we could implement a new token exchange pipeline for even better security, so our db is never leaked.
this is what needs to be done:
you can also drop some images or attachments if they help understand the issue
we need all the help we can get, so if you are coçating your left one, come write some code, but no gpt