שגיאה של Discourse OpenID Connect

סיכום מבוסס בינה מלאכותית

The discussion revolves around an error encountered while trying to connect a Discourse forum to an external Keycloak provider using OpenID Connect. Ken95 reports a NameError related to FinalDestination::FaradayAdapter when configuring the OpenID Connect settings. Alexander suggests checking the logs for more details and notes that Ken95 is using a Bitnami-based Discourse installation, which is unsupported. David identifies the error as likely stemming from an outdated Discourse core version and recommends updating to the latest stable, beta, or tests-passed version. He also emphasizes that the Bitnami image is not supported and advises using the official Standard Install for better compatibility. Attalbialami asks if Ken95 found a solution.

I want to connect an external keycloak provider to my forum.
so, I used Discourse OpenID Connect.
https://meta.discourse.org/t/discourse-openid-connect/103632/1
but, I got an error message When setting options and connecting.
I’m not familiar with Discourse, so I don’t know what to do.
Please help me.

Hi :wave:! Welcome to Discourse Meta :discourse2:

Can you share if there are any errors or warnings in /logs?

Maybe there might be a clue there :thinking:

You can also PM me if you need additional help :slight_smile:

I received this error log:

NameError (uninitialized constant FinalDestination::FaradayAdapter) lib/cache.rb:94:in `fetch' lib/middleware/omniauth_bypass_middleware.rb:50:in `call' lib/content_security_policy/middleware.rb:12:in


I see that you are using the Discourse image created by Bitnami, which is an unsupported installation.

But, depending on the error, it could be that something is wrong with the discovery document.

I would recommend you try a setup based on the official Discourse :smiley:!

This error suggests you are using an old version of Discourse core. If you update to the latest stable, beta or tests-passed version of Discourse the problem should be resolved.

I’m not sure how updating works with the Bitnami image. As @Alexander mentioned, we do not recommend or support the Bitnami image. For the best experience, we recommend the Standard Install

(post deleted by author)

@Ken95 Did you find any way to fix it ?