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

User Management #40

Open
telion2 opened this issue Dec 12, 2017 · 1 comment
Open

User Management #40

telion2 opened this issue Dec 12, 2017 · 1 comment
Assignees
Labels
DATABASE enhancement feature request FutureFeature Feature to implement in the next iteration

Comments

@telion2
Copy link
Collaborator

telion2 commented Dec 12, 2017

As the writing Note feature is going to be finished soon and the analysing of Texts is going well, we should implement a profile for users where they can log into.
This implies that we:
1.have a way for the user to login and register (UI)
2.store & retrieve authentification data in our DB
3.secure the password with encrypting methods.
4. generally secure the whole authenfication process
5. If all that is working, we need to lock the profile route and implement a way to delete stored documents of users who closed the website before registering.

  1. is already availible although still quite ugly.

  2. the DB has all the naiv columns need to store user data. Since I dont know our method of encryption yet, I dont know if there is more than that needed.
    3.&4. This where I need help. I have looked around of how some people secure such data using third-party services.
    http://www.passportjs.org/ using https://auth0.com/docs/getting-started/overview or another of their 300 authentification strategies.

  3. this would be solved by passport.js because it comes with a middleware that can lock routes.

@sven-mayer
Copy link
Member

@telion2 I used passport once and it worked out quite well. For me, it solved a lot of issues.

sven-mayer added a commit that referenced this issue Mar 6, 2018
sven-mayer added a commit that referenced this issue Mar 6, 2018
@sven-mayer sven-mayer mentioned this issue Mar 6, 2018
sven-mayer added a commit that referenced this issue Mar 19, 2018
sven-mayer added a commit that referenced this issue Mar 19, 2018
sven-mayer added a commit that referenced this issue Mar 19, 2018
sven-mayer added a commit that referenced this issue Mar 19, 2018
sven-mayer added a commit that referenced this issue Mar 19, 2018
sven-mayer added a commit that referenced this issue Mar 19, 2018
sven-mayer added a commit that referenced this issue Mar 19, 2018
sven-mayer added a commit that referenced this issue Mar 19, 2018
@telion2 telion2 added FutureFeature Feature to implement in the next iteration and removed help wanted labels Mar 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DATABASE enhancement feature request FutureFeature Feature to implement in the next iteration
Projects
None yet
Development

No branches or pull requests

2 participants