Providing Single sign on to Discourse

Single sign-on allows your Laddr instance to act as an “identity provider” for your Discourse instance, so your users only need to sign into Laddr and can seamlessly access Discourse without seeing another login prompt or registration form. If they try to access Discourse without a session, they’ll just see Laddr’s login page in place of Discourse’s and be forwarded back to wherever they were going in Discourse.

Pros of Single sign-on:

  • Less hoops for your users to jump through
  • Reduces your difficult in migrating away from Discourse in the future or adding additional tools
  • Promotes consistency in your user data across systems

Cons of Single sign-on:


  1. Visit on your Discourse instance

  2. Uncheck enable local logins and allow new registrations

  3. Check enable sso

  4. Set sso url to

  5. Set sso secret to a randomly generated string

  6. Create or override in your Laddr instance php-config/Emergence/Connectors/Discourse.config.php:

    Emergence\Connectors\Discourse::$host = '';
    Emergence\Connectors\Discourse::$ssoSecret = 'YOUR_GENERATED_SSO_SECRET';

Migrating an existing Discourse instance

If your Discourse instance has already been running for some time and has registered users, you’ll need to consider their experience when you switch to SSO. Once SSO is enabled, existing users will no longer be able to sign in with their known username + password. Just let your users know the change is happening and that as long as they register for Laddr with the same email address, they’ll still have access to their existing Discourse accounts.

If a user accidentally duplicates themselves in Discourse by signing in with a different email address in Laddr, you can delete their new Discourse account from Discourse’s admin area and then either edit their Discourse email address to match their Laddr email address, or have them edit their profile on Laddr. Next time they access Discourse they should be connected to their existing account.