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

Authentication components and routes #6

Open
2 of 5 tasks
JoseCage opened this issue Oct 19, 2017 · 6 comments
Open
2 of 5 tasks

Authentication components and routes #6

JoseCage opened this issue Oct 19, 2017 · 6 comments

Comments

@JoseCage
Copy link
Member

JoseCage commented Oct 19, 2017

This issues is related to #1 where the plan was to add authentication feature (login, register) but for now the task is to rewrite them and add new routes for that.

Note: Some features aren't finished (yet) in our core platform, like logout, password reset and recovery

  • Authentication
    • /auth/signin (Generate a new token for User and log he in)
    • /auth/signup (Register a new user and generate the token for login)
    • /auth/logout (Invalidate the token and destroy's User session)
    • /auth/password/recover (Ask for a link to reset a password)
    • /auth/password/reset (After the User receives the link in his inbox he check if he can change the passwd)

One point to pay attention: all components related to authentication should be inside src/components/auth/ organized by folders, like components/auth/password/Reset.vue and components/auth/password/Recover.vue to keep this organized..

@smkamranqadri
Copy link
Contributor

I would to do this task but can you describe what to do exactly as login and register component is already in place.

@JoseCage
Copy link
Member Author

JoseCage commented Oct 30, 2017

I would to do this task but can you describe what to do exactly as login and register component is already in place.

@smkamranqadri Thanks for your interest in helping (first of all I hope you have understood about what the project is: D).

Answering your question, yes at the moment we already have components of Login and register, however it is necessary a adjustment in them, like for example to add redirection if the login is successful or to show error to the user if there is.

@smkamranqadri
Copy link
Contributor

Every time when I supply unique user to register I got below response.

{"email":["Oops. This email isn't available!"],"username":["The username has already been taken."]}

@smkamranqadri
Copy link
Contributor

Also added logout feature.

@JoseCage
Copy link
Member Author

Every time when I supply unique user to register I got below response.

{"email":["Oops. This email isn't available!"],"username":["The username has already been taken."]}

@smkamranqadri this means the user has been (allready) registered, this is why the response is The username has already been taken.

What you seen when you tried to register at the first time?

@smkamranqadri
Copy link
Contributor

Have tried with the different user, you can try too.

JoseCage added a commit that referenced this issue Nov 11, 2017
JoseCage added a commit that referenced this issue Nov 12, 2017
* Add auth components  with local storage plugin

* Move comopnents to auth folder

* 🍰 fix token value being saved in localstorage

* 💪 Add new routes for login and register

* Add components folders and Contributing guide

* redirect handled, close #6

* removed the default user.

* change the proper mutation name.

* replace localhost for heroku endpoint
@JoseCage JoseCage reopened this Jul 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants