Re:Achilles Heel of OAuth or Why Facebook Adds #_=_
by bsimpson on Friday March 15, 2013 @01:37AM
(#5379354)
But this is only for JavaScript clients, right? I believe all the OAuth APIs I've consumed from Python send access_token in the query string.
Re:Achilles Heel of OAuth or Why Facebook Adds #_=_
by jkrems on Friday March 15, 2013 @01:49AM
(#5379380)
Maybe you are thinking of the code parameter? The one that can be exchanged for an access token in a server-to-server request?
Re:Achilles Heel of OAuth or Why Facebook Adds #_=_
by bsimpson on Friday March 15, 2013 @03:42PM
(#5382550)
I believe they're both in the query string, but you're right - code is what's sent by way of the client. access_token is exchanged between the servers.
Re:Achilles Heel of OAuth or Why Facebook Adds #_=_
by homakov on Friday March 15, 2013 @01:42AM
(#5379361)
what provider? Facebook never sends it in query string. It can also be available for Man In The Middle, in server side logs etc. Hash is supposed to be more secure.
Re:Achilles Heel of OAuth or Why Facebook Adds #_=_
by johns on Friday March 15, 2013 @02:55AM
(#5379489)
FB definitely sends access token via URL param for the server side flow: https://developers.facebook.com/docs/howtos/login/server-sid...
If there were a mitm they could get it even if it's in the hash. It has to travel to the client at some point.
hash is supposed to be more secure - not sent on server side.
but with 302 redirects it's not so secure.