[DRAFT - Needs more feedback] Add support for user specified token lifetimes #829
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.
In this branch, I updated the /users/token/ endpoint to allow specifying a shorter lifetime to address #828
It enables a new optional parameter to pass in an
expires
value in seconds, and updatesTimeExpires
model to include secondsDetails
seconds
in TimeExpires and adds support forexpires
field in formRelated issue(s)
Fixes #828
Related subsystem(s)
docs
directory)Testing
I tested these changes by adding a new test_get_token() test
Documentation
docs
directory)Swagger docs updated
Maintainability
study_id: str
)# TODO
or# FIXME
black
to format all the Python files I created/modified