Hey there everyone! I’ve been loving the hell out of the Discourse chat integration plugin, but I started to think of other ways I could integrate Discourse with Discord. I think I found a pretty neat idea - bringing Trust Levels to Discord. I’m writing a Discord bot that will allow a user to link their discourse user to their discord through the bot. Then, when the bot sees that the user has, say, trust level 2, it’ll give them a role on the server that the bot is running on. I plan to have it configurable to work with more than just trust levels, i.e, if you get admin on discourse, you get it on discord too. There are a few things I’m not totally certain on how I’m going to accomplish them, namely linking user accounts together (maybe there’s some sort of OAuth2 magic I can use?) but I think it’s a really neat idea and I’ve already gotten the bot to at least connect to both discord and discourse and allow me to see a list of commands in the bot and hot-reload them. The bot is written in node.js and fully configurable through a single json file - and setting up trust level roles in Discord is just as easy as creating any other Discord role - it’s just that the bot needs to know what trust levels get what roles. For those interested and who want to help me out with this, here’s a github repo: https://github.com/alkalinethunder/discourse-tl-for-discord

This sounds great! Happy to put some community encouragement fund behind this effort cc @erlend_sh

[图片] Stephen: There’s already a discord plugin for oauth2 authentication, have you tried it? That’d work great for giving discourse access to your discord account, but I need to give the discord bot access to both your discord account and your discourse account and basically link the two together. That way, periodically, the bot will check discourse and say “What trust level does this user have?” Discourse will tell it, then the bot will say “OK, Discord, assign this role to this user on this server because they have this trust level.” [图片] codinghorror: This sounds great! Happy to put some community encouragement fund behind this effort That sounds amazing! Would be nice to set up a demo instance of the bot that shows all the features it supports. So basically I’d set up a Discourse instance for discussion about the bot and host the demo bot on the same server as that instance, then I’d set up a Discord guild for the bot that’s linked to that aforementioned Discourse instance.

Milestone reached: The bot now lets you run discourse login and it’ll send you a message looking like this: [image] That link is VERY long, because it’s an SSO provider URL. I decided to have the bot use Discourse’s built-in SSO provider protocol to handle logins. So you run discourse login, it grabs your discord user ID (and the server’s ID), stores it in its database, generates a nonce, stores that in the database with your discord user ID, and then it DMs you a link to the forum where you can login. When you log in, Discourse will theoretically let the bot know, where the bot will then verify the SSO payload that Discourse sent it, then promptly store some of your Discourse account info in the database along with your Discord user ID and it’ll remove the nonce from your account. Man, do I need a url shortener though.

Final update for today: SSO is fully working, the bot runs an http server (no ssl just yet, maybe someone more knowledgable with Node can help set up the bot so it supports that?). So you run discourse login on the discord server, bot DMs you an SSO link, you click it, Discourse sends the bot an SSO callback, the bot validates and authenticates it, then it grabs your Discourse user ID and stores it in the bot’s database and you get a nice “Success!” message in your browser. Apparently, according to the discord bot dev community I’m in, this bot has one of the most structured codebase out of all the Node-based bots written by people in that server. Not sure how I accomplished that when my native language is C++. The bot won’t let you log in again once you’ve already linked your account - eventually it’ll have a periodic check that DMs you if it is unable to find your Discourse account, and then it’ll let you log in again. I’ve fully documented the botconfig.json file. The command interpreter received a lot of bugfixes. I’ve tested the crypto stuff in the SSO portion of the bot. The nonce expires as soon as your account is linked, so any links with that nonce expire as well and lead to an HTTP 401 when the bot gets the payload. For the same reason, refreshing the “Success” page causes an HTTP 401. Fun facts for this update: I wrote this bot in less than 24 hours while recovering from a nasty flu. Gatorade, Advil and coffee are this bot’s best friend - and mine as well, because all I have now is a sore throat. The bot is so modular in its command system that I have the overwhelming desire to port cowsay to it despite that having NOTHING to do with Discourse. But it can be done! In less than 100 lines of code!

This is a really great idea! Just so I’m clear, does it require Discourse being the SSO master?

[图片] justin: Just so I’m clear, does it require Discourse being the SSO master? Yes. It was the best way I could think of that didn’t involve forcing anyone to install an extra Discourse plugin. Instead, the bulk of the configuration is done in Discord and in the bot’s config file. I haven’t tested it with my production Discourse instance, only my dev instance (https://webber-server.bitphoenixsoftware.com/), but it does in fact work there. I have my admin account over there linked up to my local instance of the bot. My main concern is my production server redirects you to a Keycloak auth server to log in through openid connect. I haven’t tried Discourse’s SSO provider with that though, but I don’t see why it wouldn’t work. I’ll give it a try when the bot’s closer to a production state though.

[图片] Watercolor_Games: Just so I’m clear, does it require Discourse being the SSO master? Yes. If you’re already authenticated and have a signed-in session how could it tell?

Depends what you mean - before you run the bot’s discourse login command or after you’ve already done that, clicked the link it DMs you, log in, etc. Before you’ve run discourse login: When you run the command, the bot grabs your user ID from the message’s author object. It checks that ID against a json file, which looks like this: { "discord user id": { "sso_nonce": "", "sso_done": true, "discourse_uid": 0 }, "another discord user id": { "sso_nonce": "", "sso_done": false, "discourse_uid": 0 } } So it’s basically a map of Discord user IDs to objects containing an SSO nonce, a value indicating whether SSO is done for that user (they’ve logged in before), and their Discourse user ID. The bot checks if your Discourse user ID is in that file, and, if it is, then it checks if sso_done is true for that user. If so, it gives you an error saying “You’re already logged in.” If not, it generates and DMs you an SSO link, storing the nonce in that database so it can validate Discourse’s callback payload later. SSO is only used to initially grant the bot access to your user account, without the bot needing to know your credentials. Moreover, when you click that SSO link, if you’re already logged into Discourse, Discourse will just skip the login and send you straight to the bot so it can accept the login payload. After you’ve initially logged in NOTE: This is conceptual, I haven’t implemented this part yet. From now on, as long as the bot has your Discord user ID on record and you’re still on the server, it can: check if sso_done is true before doing anything related to syncing your account. use the Discourse API to query info about your trust level, groups, title, etc. Eventually I’ll add a logout command to the bot that lets you undo all syncing and remove your account from the bot’s database. Feel free to look at the bot’s code, namely: Login command that generates the SSO link: https://github.com/alkalinethunder/discourse-tl-for-discord/blob/master/commands/users/login.command.js SSO callback server - this is where Discourse’s callback payloads go: https://github.com/alkalinethunder/discourse-tl-for-discord/blob/master/sso.js

Milestone for today: I’ve added a logout command, and a profile command. Doing discourse profile will show you your own user profile: [image] If you do discourse profile , the bot will look for a user with a matching username and display its profile. This is the profile of my community admin on one of my Discourse instances: [image] It seems like I need to sanitize bio_excerpts since they contain raw HTML and Discord rich embeds don’t like that. They’ll parse links though, which is okay. Leave it to him spamming his Twitch page to unknowingly find a bug in my code :slight_smile: If the bot can’t find a user with a matching username, it’ll tell you: [image] It may even let you see discobot: [image] Actually, part of me wants to name this Discord bot ‘discobot’ because, although they don’t accomplish the same tasks, they’re both robots and related to Discourse. :slight_smile:

Discord 的 Discourse 信任等级

开发

Stephen (Stephen) 2019 年2 月 3 日 14:31 4

There’s already a discord plugin for oauth2 authentication, have you tried it?

话题		回复	浏览量
Discord Bot Construction Kit :robot: Plugin pavilion	139	24205	2024 年6 月 13 日
Discord and Discourse - Better Together \| Blog Blog	12	5319	2021 年12 月 28 日
[PAID] Discourse/Discord integration needed (roles/user groups) Marketplace	2	2547	2019 年7 月 16 日
Discourse based roles/access on Discord Feature	16	2816	2020 年1 月 29 日
Discord login and obtain discord roles in discourse Feature	3	2387	2019 年11 月 21 日

Discord 的 Discourse 信任等级

相关话题