We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The authentication should work by API. For example:
With params, we should look at user in DB and create/return user Token.
params: { "email": valid_email, "password": pwd } return: { "token": token }
With params, we should create an user in DB, and create user Token for return it.
Call logout with token in headers should remove current Token.
headers: { "token": valid_token } return: "logout success"
When authentication is done, we need to change every tests where we are authenticated.
The text was updated successfully, but these errors were encountered:
Interesting links for use email like username: https://stackoverflow.com/questions/28058326/django-rest-framework-obtain-auth-token-using-email-instead-username https://stackoverflow.com/questions/35661924/oauth2-authenticate-with-email-instead-of-username?rq=1
Sorry, something went wrong.
Currently, socializa-api use social/token/ api for obtain token.
Merge branch '#15-api-character' into #13-authentication
11e73f3
Merge branch 'dev' into #13-authentication
9c93a32
Closed #13 Authentication fixed and improved (#20)
a63424e
Virako
No branches or pull requests
The authentication should work by API. For example:
With params, we should look at user in DB and create/return user Token.
With params, we should create an user in DB, and create user Token for return it.
Call logout with token in headers should remove current Token.
When authentication is done, we need to change every tests where we are authenticated.
The text was updated successfully, but these errors were encountered: