Feat/jwt authentication setup #60
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feat: Add Docker entrypoint script for database readiness and migrations feat: Create database initialization script to set up default roles and admin user test: Implement authentication system tests for user registration, login, and role management
… registration success message
|
what SMTP provider do you intend to use? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Access token and refresh token generation via JWT, being sent on login to user
Set up Role based Authentication with endpoints to seamlessly perform CRUD operations on the role table, having default roles seeded into the role table on database initilaization
Added a new NGINX proxy to expose the swagger documentation running on http://localhost:2025/docs.
Seperated the User and Auth table, and only selected in a specific user tabel query when needed, this is to totally seperate between the users public data and the private information suchg as passwords, tokens, etc that are needed only within the
system
Integrated the flow into the existing DOCKER setup, extending the docker-entrypoint.sh which calls the init_db.py script. handling the database migrations on server start.
Commenced the mail service setup (Undone). creating a flexible token verification and token resend endpoint and service respectively, to handle all token verification depending on the "type" as described in the "VerificationType" enum.
Commented the mail sending logic in the user register flow awaiting mail service completion.
Integrating Sqlalchemy and alembic fordatabase queries and migration ease.
Yet Undone