This repository has been archived by the owner on Aug 4, 2022. It is now read-only.
Feature/jwt auth (WIP) #76
Open
Conversation
This file contains 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
Feature/jwt auth
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
PR Description
Added a jwt auth using hapi-auth-jwt2
Auth endpoints (examples added in README):
/api/auth/register (POST with email & password fields) <-- foreign scope as default. To be able to login, admin needs to change it to 'collaborator'
/api/auth/login (POST with email & password fields)
If you need to check some information inside token payload, you can access through request.auth field.
.env cfg
To modify scopes, check Hapi documentation about scope in the code, you can set scopes through feat files (server/feats/{resource}/{resource}.feat.js)
P.S: public folder is not yet regenerated to ease the PR review