Created By
Bulkan Savun Evcimen
03/15/2012 9:23pm
Subscribers (0)
Bugssigned_request does not contain user, oauth_token object after authenticating with JS api
- Status: Duplicate
- Priority: None
- Updated: March 26, 2012 at 8:05pm
Latest response from Facebook
Eric Osgood
Sorry for the erroneous status update, it was intended for bugs in a stale state. Please disregard the previous message.
March 27, 2012 at 10:40am
Eric Osgood
Hi, in order for us to repro and process this bug, we need additional information from you. If this is still an issue, please add more info to the bug. If we don't hear back from you in the next four days, we will be closing this bug. Feel free to reopen the bug if the issue resurfaces.
March 26, 2012 at 8:05pm
Lei Lei
We are already tracking this issue in another bug report. Thanks.
Marked as Duplicate of Signed Request documentation is out of date · March 16, 2012 at 1:36pm
Lei Lei
Thanks for the report. We are updating the documentation on signed request, we'll follow up when it's done.
Status changed to Assigned · March 16, 2012 at 1:35pm
After authenticating the application using FB.login (or the facebook login button plugin) the returned signed_request only contains values for algorithm, code, issued_at, user_id
| Steps to Reproduce: | 1. Go to http://www.fbrell.com/saved/c688dbc361acc32ad56b0e2e97cd7f9b 2. Click the login button and authorize fbrell. 3. Copy the signed_request that has been logged 4. Go to http://developers.facebook.com/tools/echo?signed_request<signed_request> replace <signed_request> with what was logged |
|---|---|
| Expected Behavior: | The decoded signed_request contains the values for user, oauth_token |
| Actual Behavior: | signed_request only contains values for algorithm, code, issued_at, user_id |
| API/SDK: | Javascript SDK |
| App IDs: |
|
2 people can reproduce this issue by following these steps
Repro