Skip to content
OpenID Connect Bridge for Discourse SSO
Branch: master
Clone or download
Pull request Compare This branch is 7 commits ahead, 1 commit behind fmarco76:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src/discourseOIDC
tests
.coveragerc
.dockerignore
.gitignore
.scrutinizer.yml
.travis.yml
DiscourseOIDC.py
Dockerfile
LICENSE
MANIFEST.in
README.md
config.env.py
config.sample.py
requirements.txt
setup.cfg
setup.py
tox.ini

README.md

OpenID Connect for Discourse

Travis-CI Build Status Coverage Status License

This application implements the SSO protocol requested by the Discourse forum application. The real authentication is performed by an OpenID Connect IdP configured in this app which is responsible for verifying the requests coming from Discourse and prepare the token to send back after authentication.

Based on fmarco76's DiscourseSSO.

Installation

Both Discourse and DiscourseOIDC need to be configured. Enable SSO in Discourse following the official documentation. The SSO url to is the one going to your DiscourseOIDC installation plus sso/login. For example: https://<your-domain>/sso/login.

The sso_secret is a random string and has to be the same in both services. The configuration file of DiscourseOIDC is config.py and it require the secret key (DISCOURSE_SECRET_KEY), the url of Discourse (DISCOURSE_URL), OpenID Connect IdP configuration info, among other general environment settings. There is also a map where the key is the attribute provided back to Discourse whereas the values are the name of the variables in the OpenID Connect userdata info to lookup. The name can be generated combining different values but the other accept only one value.

You can’t perform that action at this time.