Go to file
Francesco Siddi 21fef47350 Use URI.open instead of open
The 'open' method was removed in Ruby 3.0 to avoid collision with
Kernel#open. Discourse 3.0 requires this change for the plugin
to work.
2023-02-21 00:25:13 +01:00
.tx Update translations 2018-09-10 14:02:44 -04:00
bin Transifex integration 2017-12-08 15:21:07 -05:00
config Compatibility with Discourse >= 2.9 2022-11-08 15:41:07 +00:00
db/migrate Compatibility with Discourse >= 2.9 2022-11-08 15:41:07 +00:00
spec Blender ID integration 2018-10-09 13:07:35 +02:00
.gitignore Initial stab at basic OAuth2 2015-09-24 16:44:39 -04:00
Gemfile Transifex integration 2017-12-08 15:21:07 -05:00
LICENSE add License 2016-06-06 23:12:51 +05:30
plugin.rb Use URI.open instead of open 2023-02-21 00:25:13 +01:00
README.md Compatibility with Discourse >= 2.9 2022-11-08 15:41:07 +00:00

discourse-blender-id

This plugin allows you to use Blender ID as authentication for Discourse.

Plugin also supports Blender ID community badges.

How does it work?

This is how a plugin is installed.

Usage

First, set up your Discourse application remotely on your OAuth2 provider. It will require a Redirect URI which should be:

https://DISCOURSE_HOST/auth/blender_id/callback

Replace DISCOURSE_HOST with the approriate value. The OAuth2 provider should supply you with a client ID and secret, as well as a couple of URLs.

Visit your Admin > Settings > Login and fill in the basic configuration for the OAuth2 provider:

  • blender_id_enabled - check this off to enable the feature

  • blender_id_client_id - the client ID from your provider

  • blender_id_client_secret - the client secret from your provider

The plugin will also start a background job, which will run through the existing OAuth credentials and try to fetch badges for the users. The job will run every 30 minues.

Issues

Please use the GitLab project to discuss issues with the plugin, including bugs and feature reqests.

License

MIT