auth-oauth2 | A demo to learn oAuth2.0 by reverse engineering | OAuth library

Check your google developer account where you created the credentials. there should be a field named redirect URL where you should place the correct URL. This URL was used to redirect the user from modal opened on login with google.

From your ruby -v, I see that you are in an Intel x86 Mac, but the gem that your trying to build (nokogiri-1.11.3-arm64-darwin) is for new Mac ARM M1 chips. If this is the cause, it means your are using precompiled gems.

Try uninstalling the gem, specify that you don't want to use precompiled gems, and reinstall.

As you're using the current latest releases, let me explain a bit the changes in the new API. In 4.0.0 we're split authn and authz so in your example you already perform authn correctly and get a User object instance.

Now you want to extract permissions, as you're doing JWTAuth you're taking the "low" level path, while if you'd be using OAuth2Auth some things would be not necessary (such as loading of keys, etc...).

Now that you have a user object you need to have a authz extraction object. For this I'll be exemplifying with the java API but in Kotlin it should be quite similar:

Thanks to @Les Nightingill, I found the issue.

It was not directly linked to assets generation, but the probleme was indicated at the first error line in the logs :

I think I see what's going on. In your Dockerfile, change your DB_URL from: mysql:// to mysql2://

You are loading the mysql2 gem, but indicating to ActiveRecord that you want to use a connection via the mysql gem.

This is probably and error with the stylesheet_link_tag and stylesheet_pack_tag, check out your layout files probably you are including sass files and you are using stylesheet_link_tag, this is breaking your code given that as I understand you can just link plane css files. so if you are including sass files use the stylesheet_pack_tag

I figured out what the problem was. On the google developer console for my app, on OAuth 2.0 Client IDs, I had created an ID with type "Other" instead of "Web application".

Creating a new one on https://console.cloud.google.com/apis/credentials?project=myproject with the type "Web application" and adding the callback url (both http and https) to Authorized redirect URIs solved the problem.

From what it looks like is you are having a network issue where Faraday isn't set up to wait long enough for a response. All I can really tell from the trace is that somewhere along the trail to facebook and back you're encountering network issues.

A couple of things I can think to check:

• If your site is running through HTTPS, ensure your certificate is working properly.
  • Check that your gemfile is set to require a specific version of omniauth-facebook that is compatible with your version of Rails and dependencies.
  • Extend the timeout length for Faraday
  • Use a retry gem like https://github.com/ooyala/retries to try and give the network enough time to respond before Faraday closes the connection.

A few other people have commented on this issue in omniauth-facebook's github https://github.com/mkdynamic/omniauth-facebook/issues/283

The root of the problem seems to be bundler. What operating system and Ruby version are you using? It may be a problem with old OpenSSL library, so you can not install bundler and everything after it.

If you are using jRuby (your gem list output tells so), your problem seems to be the same as described in link. And there is a solution as well.

Maybe you forgot to set 2.1.2 version of ruby as global? (rbenv set global 2.1.2)