-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
bad or missing username when authenticating with Twitter #4291
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
Comments
Can you provide the logs when running with VERBOSE=1?
|
@casajavi I just had a look at the source code, and the only way to get 'bad or missing username' error is to neither provide authData nor a username on this This probably means that the payload is malformed, I managed to get this:
So I guess that's probably the way your payload is formed/malformed. |
@flovilmart Ok I wasn't including the correctly formatted payload but yea now I get the error you get.
now I am in the same spot hahaha.... so why is this error happening ? Is this suppose to create a new user or only link twitter to an existing user? |
yeah so double check your auth_token, secret, and configuration. I believe there's an API explorer on twitter, so you can double check that all those parameters are valid. |
Issue Description
I am trying to use the Twitter authentication through the Rest API and I keep receiving this error:
I have set up the parse server with the necessary data as follows:
and I am sending a POST to
/users
with the following payload:I could not find any documentation detailing on how to achieve this and most of what I have tried has been from following the conversation on the PR by @flovilmart that added this functionality.
Maybe I am doing something wrong, if anyone has any suggestions I would appreciate it.
Steps to reproduce
The following command:
Expected Results
A new parse user should be created
Actual Outcome
The following error is thrown:
bad or missing username
Environment Setup
Server
Database mLab, ObjectRocket, Digital Ocean, etc): mLab
The text was updated successfully, but these errors were encountered: