# Disable DiscourseConnect
**URL:** https://meta.discourse.org/t/disable-discourseconnect/119029
**Category:** Integrations
**Tags:** sso, discourseconnect, how-to
**Created:** [May 29, 2019, 7:49pm UTC](https://meta.discourse.org/t/disable-discourseconnect/119029 "2019-05-29T19:49:16Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Discourse](https://meta.discourse.org/u/Discourse)
#### Post date: [May 29, 2019, 7:49pm UTC](https://meta.discourse.org/t/disable-discourseconnect/119029/1 "2019-05-29T19:49:17Z")
So you’ve been using [DiscourseConnect](https://meta.discourse.org/t/official-single-sign-on-for-discourse-sso/13045) on your forum, and now you want to turn it off? Then this guide is for you!
Discourse uses email addresses as the primary identifier for a user. Once [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) is disabled, users will need to go through the password reset process to reset (create) a password.
> ⚠ This guide assumes your [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) provider shared real user email addresses with Discourse. If [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) provided `.invalid` emails or other emails that the user would not know, this guide will not work.
1. Decide on a time to make this change (removing [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true)).
2. Alert your community of the upcoming login change, and inform them of the planned change time. There will not be any downtime or read-only mode time required, but registration/login may be impacted during the switch.
How you alert your community is up to you and your team, but my suggestion would be either a globally pinned topic or a banner topic.
3. Prior to the change, configure any social providers you want to work. Complete all required steps except for the “enable xyz logins” site setting within Discourse. You want everything ready to go, but not enabled yet.
[Configure Google login for Discourse](https://meta.discourse.org/t/configure-google-login-for-discourse/15858)
[Configure Facebook login for Discourse](https://meta.discourse.org/t/configure-facebook-login-for-discourse/13394)
[Configure Discord Login for Discourse](https://meta.discourse.org/t/configure-discord-login-for-discourse/127129)
[Configuring X login and rich embeds for Discourse](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395)
[Configure GitHub login for Discourse](https://meta.discourse.org/t/configure-github-login-for-discourse/13745)
[Configure LinkedIn login using OpenID Connect](https://meta.discourse.org/t/configure-linkedin-login-using-openid-connect/305366)
4. When you’re ready to go, uncheck the `enable discourse connect` site setting, check `enable local logins`, and check `enable xyz logins` for any social provider you configured.
5. Be sure to test all the login options you enabled and make sure they work.
You’ll likely also want to create a topic/guide explaining to users how to log in given the changes. This may be the same topic as the “upcoming login change”, or something else. Users who choose to login with a social provider should “just work” as long as they use the same email for the social provider as they did for SSO. Users who would rather use a username and password will need to go through the “I forgot my password” process to create a password.
> Last edited by @JammyDodger 2024-05-26T07:22:27Z
>
> > **Check document**
> >
> > Perform check on document:
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [September 7, 2022, 6:28pm UTC](https://meta.discourse.org/t/disable-discourseconnect/119029/2 "2022-09-07T18:28:44Z")
For the sake of completion.
> [@Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso)](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/1):
>
> ### What if you check it by mistake?
>
> If you check `enable_discourse_connect` by mistake and need to revert to the original state and no longer have access to the admin panel, visit `/u/admin-login` and follow the instructions.
>
> OR, from server console run:
>
> ```plaintext
> cd /var/discourse
> ./launcher enter app
> rails c
> irb > SiteSetting.enable_discourse_connect = false
> irb > SiteSetting.enable_local_logins = true
> irb > exit
> exit
>
> ```