Discourse를 OAuth2/OIDC Provider로 지원하기

:information_source: Summary Oauth2/OIDC Provider. Users can create their own apps.
:hammer_and_wrench: Download Link https://vvpp.cc/s/GPmCV

Features

We know that Discourse officially does not use Discourse as a solution for an Oauth2/OIDC Provider.

To better implement the service and to allow everyone to bring more creativity into NL, NL has implemented an Oauth2/OIDC Provider based on Parkour-Vienna/distrust: Use discourse as an OIDC (OAuth 2.0) provider, which allows users to apply for applications themselves.

Configuration

I used Mysql to store user-related data, so the specific usage method is to first install Mysql/MariaDB, execute the Sql script to create the database; then configure distrust.yml, set the database-related content, and then execute distrust genkey to generate the corresponding rsa key; then create a discourse connect provider in the Discourse backend and enter the relevant information.

Then execute

chmod _+x distrust
./distrust

Access your IP:3000/apps to see the application interface.

Demo

When user use Oauth2/OIDC login.

5개의 좋아요

This seems to be the piece I was looking for but I’m not technical, so I will patiently wait until someone looks into it :slight_smile:

I’m sharing the OP translated to english with DeepL.

1개의 좋아요

An excellent beginning; I am grateful for your open-source contribution. This truly marks a magnificent commencement. :clap: :clap: :clap:

cool!

./distrust

mysql 버전:9.0.1

오류:

FTL 데이터베이스 초기화 실패 error=“데이터베이스 마이그레이션 실패: 고유 인덱스 생성 실패: Error 1064 (42000): SQL 구문에 오류가 있습니다. MySQL 서버 버전에 해당하는 매뉴얼을 확인하여 ‘IF NOT EXISTS idx_user_authorizations_user_client \n\t\tON user_authorizations(user’ 근처의 올바른 구문을 사용하세요” at line 1