A user seeks to integrate JWT-based Single Sign-On (SSO) with Discourse for their Play 2.5 application, aiming to redirect users to their app for authentication and return a JWT token to Discourse. They found two JWT-related plugins but are unsure which to use. eviltrout recommends the official JWT Plugin, noting it’s production-tested, and points to a guide for plugin installation. Later, BalintH asks whether the JWT plugin is available for non-self-hosted Discourse instances, since it’s not listed under business plans. eviltrout clarifies that JWT support is not included in Discourse’s business tier and strongly advises using OpenID, OAuth2, or DiscourseConnect instead, asking if JWT is their only authentication option. The discussion highlights a gap for hosted Discourse users needing JWT SSO, with official support currently limited to self-hosted deployments.
We are investigating using Discourse as a forum section for our website. Our existing app is a Play 2.5 application with it’s own login setup and a JWT authenticator. Our goal is to implement some form of single-sign-on setup where users will be redirected (from Discourse) to our Play app to authenticate, the JWT token is created and sent back (via redirect) to Discourse for use in validating subsequent actions.
Hi, we are trying to implement a similar flow as in the original post. I checked the JWT plugin, and the installation guide, and it seems that it only describes how to install on self-hosted instances, and the plugin was not listed under any business plan. So my question is, how is it possible to use the JWT plugin with a non self-hosted instance?
Unfortunately we don’t include the JWT support in our business tier and strongly recommend you use OpenID, OAuth2, or DiscourseConnect. Is that your only option for auth?