facebook-authentication

问题 Upgrading our Facebook iOS integration from the 2.x SDK to 3.x SDK automatically logs users out who were previously logged in, since the authentication credentials that we used to have to manually handle ourselves are now handled behind-the-scenes by the new SDK. Is there any way to force the 3.x SDK to authenticate using the access token and expiration date that we were previously manually storing, as a one-time authentication migration? Thanks in advance! 回答1: Finally figured it out. The

问题 I am going through the facebook authentication process to log my users into my site. Once a user is logged in I redirect to the profile page using: resp.sendRedirect("/l/profile"); But when I get to the profile page, the URL ends /profile#_=_ This seems to be at the end of the URL redirected by facebook when it returns a code. Why is it sticking around, how do I get rid of it? 回答1: I'm guessing it's a byproduct of new feature called "Authenticated Referrals" whereby they add a valid

问题 My current user story is that user1 is logged into my website and facebook (these accounts are connected etc). User1 logs out of my site but not facebook. After this user2 logs into his account, but the left over session from user1 screws with user2's interaction with my site and who they post as. So to fix this I made it check if the user who is logged in actually owns the currently logged in facebook (this would result in them going to facebook log out etc) and it shows a link that should

问题 My current user story is that user1 is logged into my website and facebook (these accounts are connected etc). User1 logs out of my site but not facebook. After this user2 logs into his account, but the left over session from user1 screws with user2's interaction with my site and who they post as. So to fix this I made it check if the user who is logged in actually owns the currently logged in facebook (this would result in them going to facebook log out etc) and it shows a link that should

问题 I am using FirebaseUI-Authentication . Signing in with an email or a Google account is successful, but sign in with Facebook doesn't work. onActivityResult() is not called after AuthUI activity was started and attempted to sign in with Facebook. After sign in attempt the app is stuck at the loading window. logcat outputs a FirebaseApp log: Notifying background state change listeners. On the Facebook app dashboard I set the Valid OAuth redirect URI , as the firebase guide stated, and I set the

问题 We have 2 Android activities (activity A and activity B) Suppose that we instantiated a Firebase reference in activity A. Activity A also handles all user authentication (Facebook, Google, and email/password). Activity B, which is started from activity A using an Android intent, should use the Firebase reference to access some data on the Firebase servers. Now I was wondering what the best design is to send the Firebase ref from activity A to activity B. Bundle the Firebase reference with the

问题 We have 2 Android activities (activity A and activity B) Suppose that we instantiated a Firebase reference in activity A. Activity A also handles all user authentication (Facebook, Google, and email/password). Activity B, which is started from activity A using an Android intent, should use the Firebase reference to access some data on the Firebase servers. Now I was wondering what the best design is to send the Firebase ref from activity A to activity B. Bundle the Firebase reference with the

问题 Preface I'm developing several web services and a handful of clients (web app, mobile, etc.) which will interface with said services over HTTP(s). My current work item is to design an authentication and authorization solution for the product. I have decided to leverage external identity providers, such as Facebook, Google, Microsoft, Twitter, and the like for authentication. I'm trying to solve the problem of, "when a request comes to my server, how do I know who the user is and how can I be

问题 Update This was reported to Facebook via https://www.facebook.com/whitehat/report/ on Dec 16th 2013 and Facebook responded on Dec 17th that the bug has long since been fixed . I have retested this with my Facebook account (that I still haven't verified the email address on) and when using the Grap API Explorer tool it is not possible to get the email address of this account using the Graph API or using a FQL query. Conclusion: The email address you get from Facebook using the Graph API or a

问题 Update This was reported to Facebook via https://www.facebook.com/whitehat/report/ on Dec 16th 2013 and Facebook responded on Dec 17th that the bug has long since been fixed . I have retested this with my Facebook account (that I still haven't verified the email address on) and when using the Grap API Explorer tool it is not possible to get the email address of this account using the Graph API or using a FQL query. Conclusion: The email address you get from Facebook using the Graph API or a