Skip to content
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

Improving security using 2FA #856

Closed
indiandragon opened this issue May 25, 2018 · 12 comments · Fixed by #1624
Closed

Improving security using 2FA #856

indiandragon opened this issue May 25, 2018 · 12 comments · Fixed by #1624
Labels
state:released Released as stable version state:released-beta Released as beta version type:feature New feature or improvement of existing feature

Comments

@indiandragon
Copy link

Hi team,
Have any of you implemented Two factor authentication (2FA) for Parse dashboard, it's very crucial that we have better security implemented for the dashboard.

Would love to hear any security augmentations you've made for your parse-dashboard.

@flovilmart
Copy link
Contributor

At the moment we haven’t but I believe this should be possible with a custom passport authentication or else.

@mnlbox
Copy link

mnlbox commented Jun 18, 2018

@indiandragon, @flovilmart Guys you can see some link and library about implement 2FA in node.js in this issue:
strapi/strapi#786

Maybe useful for someone. 😉

@flovilmart
Copy link
Contributor

@mnlbox if we implement 2FA this is probably gonna go through a passport.js plugin as this project is already in used in the dashboard.

@mnlbox
Copy link

mnlbox commented Aug 5, 2018

@flovilmart is it possible to implement 2FA with cloud code and web-hook?

@flovilmart
Copy link
Contributor

You can implement your own login mechanism in front of the dashboard, independently of the dashboard

@stale
Copy link

stale bot commented Jan 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label Jan 10, 2019
@stale stale bot closed this as completed Jan 17, 2019
@dblythy
Copy link
Member

dblythy commented Nov 17, 2020

If you'd like to reopen this, I'm happy to work on it @TomWFox.

@stale
Copy link

stale bot commented Jan 10, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 10, 2021
@mtrezza
Copy link
Member

mtrezza commented Jan 10, 2021

Maybe this can now be easily achieved with parse-community/parse-server#7079.

@stale stale bot removed the stale label Jan 10, 2021
@mtrezza mtrezza added type:feature New feature or improvement of existing feature and removed state:wont-fix Won’t be fixed with a clearly stated reason labels Jan 10, 2021
@parseplatformorg
Copy link
Contributor

🎉 This pull request has been released in version 3.3.0-alpha.1

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Oct 8, 2021
@mtrezza mtrezza removed the state:released-alpha Released as alpha version label Oct 8, 2021
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 3.3.0-beta.1

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Nov 1, 2021
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 3.3.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Jan 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-beta Released as beta version type:feature New feature or improvement of existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants