Our organization is merging with another, and in doing so, we’re combining user bases (our Discourse site, and our new main site). We want to retain the native login experience on our Discourse site, but we want to use Discourse as the identity provider for the new site. Meaning, user goes to new site, clicks login, redirects to Discourse, verifies identity, and returns to new site with Discourse credentials. All while retaining the native Discourse login experience for those that go to the Discourse site directly. Use Discourse as an identity provider (SSO, DiscourseConnect) ← This references using enable discourse connect provider to turn this SSO setting on. However, in another article, it says that enable discourse connect disables the native Discourse login experience. My question is, will running enable discourse connect provider disable the native Discourse login experience like enable discourse connect does?

No, you can enable the provider and won’t affect your login flows.

Нативный вход + провайдер идентификации

supermathie (Michael Brown) 07.Май.2026 01:59:20 2

Нет, вы можете включить провайдера, и это не повлияет на ваши процессы входа.

Тема		Ответов	Просм.
Reverse Single-Sign-On: Possible to use Discourse accounts on my other site? SSO	2	1789	30.03.2017
Communities using discourse SSO for their in-app community experience SSO	1	316	25.07.2024
Can I use DiscourseConnect along with Discourse Native Registration? SSO	1	758	04.10.2022
Enabling Login to Discourse from a third party api SSO rest-api	4	1719	25.08.2022
Using Discourse as an authentication provider SSO	1	1960	10.06.2021