Error: OAuth.io / oauthd responded with : POST is not allowed

[iamlogiq]

@william26 Thanks for fixing the previous issues! Great help but now there is a new error message: 'POST is not allowed'. here's the code i'm using on my backend after i've obtained the state_token and the auth_code:

OAuth.auth(req.params.api, req.session, {
code: req.params.authCode
})
.then(function (request_object) {
return request_object.get('/me');
})
.then(function (info) {
var user = {
email: info.email
};
res.send(200, 'Successfully logged in');
})
.fail(function (e) {
res.send(400, 'An error occured: ' + e);
});

[william26]

I tried your code and it seemed to be working just fine. Is the req.params.api correctly set?
Is the SDK correctly initialized? Which provider are you using?

[iamlogiq]

Here is a representation of my code:
OAuth.setOAuthdURL('https://mywebsite.com', '/auth');
OAuth.initialize('my app key', 'my app secret');
// I've replace req.params.api and req.params.authcode with:
OAuth.auth('facebook', req.session, {
code: 'my code goes here'
})
I have deployed 2 apps on heroku, my backend with my server logic and a separate app that runs oauthd.

I'm thinking it might have to do with req.session? what is the SDK doing with the session data?
What about the credentials option in OAuth.auth()? Should I be adding the user credentials:
OAuth.auth('facebook', req.session, {
code: 'my code goes here',
credentials: "what goes here?"
})

[william26]

The origin of the POST error is usually a call made on the wrong address.
Have you updated the base field in the config.js file of oauthd?

[iamlogiq]

No i didn't. right now it's set to "/"
if i change it to "/auth" the application crashes before loading

[iamlogiq]

I should mention that this is the version of oauthd i'm using since it's the one that works on heroku with a reddis database
https://github.com/thyb/oauthd-heroku

[william26]

If it's set to "/", you should do this before initializing:

OAuth.setOAuthdURL('https://mywebsite.com', '/');

The second argument tells the SDK what is in the base field of your server.

Hope this helps, sorry I wasn't clear about that.

[iamlogiq]

I'm a little more confused now... doing this: OAuth.setOAuthdURL('https://mywebsite.com', '/') gives me the same error as before: State is missing from response.
Right now the state field in oauthd is set to "/' and when i set the state in my backend using OAuth.setOAuthdURL I get 2 separate error: if state is "/" I get "state is missing from response" and if I change it to "/auth" I get teh POST error.

I"m not sure what else to do and desperately trying to make it work.

[iamlogiq]

Can anyone help??

[william26]

Hi,

Sorry for the delay. What happens if you set the base field in oauthd to /auth?
The "state is missing from response" error can have several causes:

• An error from oauthd
• A problem with sessions (if your user's cookies are reset between the call to the state endpoint and the call to the authentication endpoint, the SDK won't find the state token generated in the first endpoint, as the session is not the same anymore)

To get more information, you could actually go in the SDK's code, in the node_modules/oauthio/js/lib/authentication.js file. In the authenticate method, you'll find a callback to a POST request, in which you can add a console.log to see what's really returned by oauthd:

request.post({
        url: cache.oauthd_url + cache.oauthd_base + '/access_token',
        form: {
          code: code,
          key: cache.public_key,
          secret: cache.secret_key
        }
      }, function(e, r, body) {
            console.log(body); //This will give you the body of oauthd's response
            //...
      });

What SDK are you using on the client-side? JavaScript? Or another one?

Hope this will help :)

[iamlogiq]

Thanks for the help again @william26 I got a chance to do what you suggested and i'm getting this message from the console.log:

{"status":"error","code":405,"message":"POST is not allowed","data":{"code":"MethodNotAllowedError"}}

What does that mean? any clues as to what the problem is? To answer your question, on the front end i'm using the javascript sdk installed via bower