A user, barreeeiroo, wants to integrate their Discourse community with a Discord server using the Discourse Bot plugin. This requires enabling Discord Login, but they want to keep using their custom OAuth2 solution and allow Discord accounts linking.
barreeeiroo asked if it’s possible to enable the /auth/discord URL without enabling the login option. Falco suggested hiding the Discord button on the login modal with CSS, but barreeeiroo explained that this doesn’t achieve their goal, as it still forces the modal to appear and changes the login flow.
Falco provided a solution, a GitHub repository discourse-excluded-logins, which barreeeiroo confirmed is exactly what they were looking for.
We are currently integrating our Discourse community with a Discord server. We are using the Discourse Bot plugin. However, it requires to enable Discord Login to work.
We want to keep using our custom OAuth2 solution, but at the same time, allow Discord accounts linking.
Is there any way to enable the /auth/discord URL without actually enabling the login option?
The easy thing here is just hidding the Discord button on the login modal with CSS.
Yeah, but this is not what we actually want to achieve. We already did that. 
By hiding the button with CSS, you still force the modal to appear. Previosuly, by clicking the “Log In” button, it redirected to our OAuth2 server, and user was logged in with a single flow. Now, they see a modal and have to click in “with OAuth2”.
Is it possible to forward users to the OAuth2 when clicking “Log In”, having 2 auth options available?
With two options enabled, and hidding with CSS, users see this:
Ideally, they should be redirected to the OAuth2 flow as soon as they click the “Log In” button.
Me and @Roman worked in a solution to this exact problem years ago. It wasn’t open source because it is quite a niche use case, but here it is:
Thank you! That is exactly what we were looking for. 
