This repository has been archived by the owner on Jul 30, 2024. It is now read-only.
Custom request loader #262
Closed
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
|
I'm not sure I understand the motivation here, nor do I see this as a necessary feature. |
|
I couldn't find a way to have integration between the web (i.e. the user register, and the admin assign roles) and a REST API which allows the user to do actions. |
|
I'm afraid this is not a feature I want to support. |
galeo
pushed a commit
to galeo/flask-security-outdated
that referenced
this pull request
Mar 4, 2020
) I can actually reproduce the bug report - unless the OP actually overrode the default form and didn't put in a phone number. But that's fine - simple and easy fix. closes: pallets-eco#262
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.
Flask-login allows authenticating every request through a request loader (i.e. rest API auth)
and added the request loader, the api key generation is for now left to the user (i implemented it as hash of the concatenation of user email and concatenation of random/secret data) and it could be added to the UserMixin class.
there's also this p.r. for flask-login maxcountryman/flask-login#163 to avoid having unneeded cookies, at the moment is a global config, but it could be hacked to ensure that if it's a request for the request loader session can be cleaned, but would require more effort.