My app has Facebook Login. It has suddenly stop working. It is always login user as anonymous, so I am not getting any data. How to stop anonymous login for my App.
OAuthException, code: 100, message: (#100) Tried accessing nonexisting field (first_name) on node type (AnonymousUser), x-fb-trace-id: EQfRXtpQzk4 [HTTP 400]
SDK version 5.5.1 GA
This is a Facebook issue and there is an opened bug on their platform:
https://developers.facebook.com/bugs/173424853153369/
Related
I was following the great article How to Use Ionic 4 for JHipster 6 to Build a Mobile App, and want to stay on Keycloak as a identity provider (for now :) )
I follow the article and pass successfully the generating, running and authenticate to app with built in credentials admin/admin.
At the second step I generated and run ionic app and typed:
cd mobile
ionic serve
and I got my mobile app running with login screen.
I typed again admin/admin and got folowing outhput in my backend app console:
2020-05-16 16:19:08.094 WARN 12590 --- [ XNIO-1 task-56] o.z.problem.spring.common.AdviceTraits : Forbidden: Could not verify the provided CSRF token because your session was not found.
2020-05-16 16:19:08.097 WARN 12590 --- [ XNIO-1 task-56] .m.m.a.ExceptionHandlerExceptionResolver : Resolved [org.springframework.security.web.csrf.MissingCsrfTokenException: Could not verify the provided CSRF token because your session was not found.]
And of course i can't login to mobile app. I did not change anything related to Octa things (because it is Octa specific)
How can I enable and successfully log in to generated Ionic4 mobile app using Keycloak instead of Octa identity provider?
In my react-native app I give the user the possibility to log in with a Facebook button.
For this purpose I use Amplify, which in Cognito should create a user in a user pool.
This works too, but for some reason it does not always work.
I can't explain it either, because I don't use triggers that might contain a bug from my site.
The login does not work in about 40 percent of the cases.
The following actions lead to the error:
The user clicks the facebook button
The user will be forwarded to facebook
The user logs in to facebook
The user will be forwarded back to the react-native app.
Result: Now no user is created in the user pool and the following errors appear in the react-native app (via Hub.listen("auth"):
{"event":"signIn_failure","data":{},"message":"The OAuth response flow failed"}
console.js:35
{"event":"signIn_failure","data":{},"message":"The OAuth response flow failed"}
console.js:35
{"event":"cognitoHostedUI_failure","data":{},"message":"A failure occurred when returning to the Cognito Hosted UI"}
console.js:35
{"event":"cognitoHostedUI_failure","data":{},"message":"A failure occurred when returning to the Cognito Hosted UI"}
console.js:35
{"event":"customState_failure","data":{},"message":"A failure occurred when returning state"}
console.js:35
{"event":"customState_failure","data":{},"message":"A failure occurred when returning state"}
My app-client settings look like this:
In my react-native app on android, I get an error when I try to login with facebook using the following call,
Parse.FacebookUtils.logIn(<scope>)
This is the error I get,
{
code: undefined,
message: 'unauthorized',
line: 10800,
column: 21,
sourceURL: 'http://localhost:8081/index.android.bundleplatform=android&dev=true&hot=true&minify=false'
}
I have the initialization code as shown below,
Parse.initialize('myapp');
Parse.serverURL = `${serverURL}/parse`;
FacebookSDK.init();
Parse.FacebookUtils.init();
I am also setting the facebookAppIds as mentioned in the Readme for parse-server
The facebook login part works fine, as in the app gets access to the user profile but the user account is not created on the parse-server. I don't know if I need to use any other key for the server.
I'm trying to get Facebook authentication working with Devise through omniauth-facebook, I've followed the instructions here: https://github.com/plataformatec/devise/wiki/OmniAuth%3a-Overview
When I follow the login with Facebook link I am redirected to Facebook to login and accept the requested permissions.
I am then taken back to /users/sign_in with the error message "Could not authorize you from Facebook because "Invalid credentials""
Looking at the server logs the redirect comes from "/users/auth/facebook/callback?code=[long text string]" which is being processed with Users::OmniauthCallbacksController#failure rather than Users::OmniauthCallbacksController#facebook as I would have expected if it had worked.
Any suggestions as to why this is happening and how to resolve it much appreciated.
Ok, I had the very same issue. The reason for me turned out that I had defined this line in config/initializers/devise.rb:
config.omniauth :facebook ...
The app id and app secret were defined for my test Facebook app, and for production one. Fixing those id:s now fixed the problem.
facebook changes protocol from oauth to oauth2
the main difference that credentials (id, token, name..) now packaged into one hash. You should parse.
I'm facing a weird problem.
I followed this tutorial : https://github.com/plataformatec/devise/wiki/OmniAuth:-Overview
It works perfectly with the exact same code on my local machine (with modification on APP_ID and SECRET).
But when I test it on another server, I cant get logged in with Facebook informations...
I click on the link (<%= link_to 'register with fb', user_omniauth_authorize_path(:facebook) %>) then I'm redirected well to Facebook which asks me if I allow the app and finally I get redirected to my site.
But I'm redirected to /user/sign_in ! And no record with the user retrieved from Facebook is created.
The log gives me :
Started GET "/users/auth/facebook" for 192.168.1.254 at 2011-07-25 19:06:11 +0400
Started GET "/users/auth/facebook/callback?code=grV09GQr[...]BbcM-mxklOu5E"
for 192.168.1.254 at 2011-07-25 19:06:12 +0400 Processing by
Users::OmniauthCallbacksController#failure as HTML Parameters:
{"code"=>"grV09GQrqjDepasyQpVhqSg0FINlr4h9[...]sSUooMrBRxBbcM-mxklOu5E"}
Redirected to http://mysite.com/users/sign_in Completed 302 Found in
1ms
Someone has an idea ?
Many Thanks
You are getting the sign-in page because this is the default behavior for the omniauth gem when an error occurs from facebook. You are getting rejected from facebook. If you were to decode the code in the returned URL, you might be able to figure out the reason. It would be helpful if the error handler did that.
With facebook connect you must put the url of your website in the facebook configuration. It is the canvas URL or web site url/domain in the configuration. If you don't have this set correctly, then facebook will reject your return request.