200-Added-authorization.js-and-authentication.js-for-access-management #402
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.
Pull Request: Feature - Added Authorization Middleware
Addressed: issue #200
This pull request introduces a new feature to enhance API security using the
authorization.js
middleware. It is designed to determine whether a user can access a protected API route. Here are the key points:Changes:
authorization.js
middleware.authorization
middleware for access control.User.js
modelUsage:
To utilize this feature, follow these steps:
User Authentication: Users must log in and obtain a JWT access token.
Access Token Placement: The access token should be included in the HTTP request headers as follows:
For Development team:
.env
file.env
file just add a new variableSTATE
=Development