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

API: should use an identity token #7

Open
Kernald opened this issue Oct 3, 2013 · 0 comments
Open

API: should use an identity token #7

Kernald opened this issue Oct 3, 2013 · 0 comments
Assignees

Comments

@Kernald
Copy link

Kernald commented Oct 3, 2013

The API currently uses the email/password in each request to identify the user. A better way to do it would be:

  • Replace the POST user/auth_gtg method by a GET method, taking as parameters the email and password, and returning an API token if auth is successful, null if unsuccessful.
  • Replace the email/password couple by the token in every other call

Ideally, the user/auth_gtg method should take an additional parameter, an app ID. If not used right now, it could be useful later to let the user revoke specific tokens.

@ghost ghost assigned parinporecha Oct 3, 2013
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