New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update/add Flask-Security-Too #35
Comments
Hey @jwag956 how are you? So, last time I checked, flask-security had a new maintainer. That is exactly why I put it back into the extensions list (flask-security-fork was being used). I would like to try and involve them in the loop before taking action, given flask-security popularity. |
Thanks - yes - there was - but nothing came of that - which is why I started my own, at first I just released existing/approved PRs - then started modernizing. |
Seems flask-security is left to the moths. Mind if we discuss flask-security-too a bit @jwag956 ? Gonna ping you privately for some details but would like to know a few things: PS: Thank you for opening this ticket and bringing my attention to this major issue. |
Sure - my email is on my profile. Right now - it's just me - I have had around a dozen PRs - mostly small - although the two-factor auth PR was a large feature done by someone else. |
It is done. |
For the past 6 months I have been resurrecting Flask-Security - alas requiring my own fork at:
https://github.com/jwag956/flask-security
The original Flask-Security basically has stopped being maintained. I would like to either
ADD Flask-Security-Too as an additional supported extension OR replace Flask-Security.
I am willing to do the PR - just want guidance/approval of the idea.
The text was updated successfully, but these errors were encountered: