Lmvp Authentication with Swagger Visualisation #25
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
added 4 commits
August 2, 2020 10:12
-Added Swagger, to allow better visualisation of API(added in requirements.txt file). -Added Authentication app, which allows users to register. -Added Email Verification, which sends users verification tokens, which can then be successfully verified on the API (Email used is a test Gmail account. Details are in the setting.py file in ‘webapp’. - Added all Serializations and Models required to, register verify and login Users -Added Jwt for token generation (added in requirements.txt file) -Two tokens are generated, refresh and access - Added login through Swagger interface, which requires users to input generated token, to access information from the API. -Added Renderers in order to ensure consistent responses in the API, especially when an error is generated.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As requested, I separated the two branches. Making this one have swagger installed for API Visualisation. Take a look at both and then you can merge whichever seems more suitable for the project. If you need help using swagger just reach out and ill explain accordingly.
No Bugs or Issues found so far.
Next, I would like to finish the development of authenticating users to access information from the lmvp interface. This will restrict all information until the token is provided or User has logged in.
Would you prefer having a username/password combo or an access token generated upon registration?