oauth version: authorization step
-
the client is a mobile application.
the client app will not present the UI to the user, it only need to use oauth, so it can make various API calls on the users behalf. So no individual account are required, like for Twitter for example, the authorization step will be invisible to the user. The username and password will be hardcoded in the app.
I am able to get a Request token correctly: my token matches the server generated one, and the server sends me back the oauth_token.
Next I am trying to authorize using that oauth_token, and the hardcoded username/password.
This is the step I am having problems with.
The first question is: am I going at it the right way? Is this something that will work? All the apps on many devices will log in with the same username and password so they can make various API calls.
The second question: does wordpress have a non-ui login where you can provide the username/password and responds with the auth_verification that you can use for the access token oauth final step?
- The topic ‘oauth version: authorization step’ is closed to new replies.
