# הגדרת DiscourseConnect - מערכת כניסה אחת רשמית ל-Discourse (sso)
**URL:** https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045
**Category:** Integrations
**Tags:** sso, discourseconnect, configuring, how-to
**Created:** [25 בפברואר, 2014, 8:30am UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045 "2014-02-25T08:30:34Z")
**Posts on this page:** 7
**Page:** 3
### Author:  [@devaoc](https://meta.discourse.org/u/devaoc)
#### Post date: [6 באוקטובר, 2025, 6:59pm UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/621 "2025-10-06T18:59:36Z")
Is there no way to test adding [Discourse connect](https://meta.discourse.org/t/13045?silent=true) on the Hobby plan? I want to test this out before paying… However, I don’t see the settings options for enabling [Discourse connect](https://meta.discourse.org/t/13045?silent=true).
Edit: I’ve asked the Discourse assistant this same question and it looks to be the case. Correct it if its wrong though because I’d rather not pay for this until I know that I need to.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [7 באוקטובר, 2025, 3:48pm UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/622 "2025-10-07T15:48:06Z")
[DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) is available on the Pro plan. You can start a free trial on that plan and test it for free. (You will only be charged if you decide to start a paid subscription.)
---
### Author:  [@adopilot](https://meta.discourse.org/u/adopilot)
#### Post date: [13 בנובמבר, 2025, 12:50pm UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/623 "2025-11-13T12:50:43Z")
> [@Discourse](#):
>
> ### Advanced Features
>
> - You can pass through custom user fields by prefixing the field name with `custom`. For example `custom.user_field_1` can be used to set the value of the `UserCustomField` that has the name `user_field_1`.
Is there any convention or rules how to encode user field names.
If my custom user fields are named as eg:
- Šifra za kasu
- Vaše radno mjesto
How I should format my payload Do i need to urlencode name or is enough to use snake case only
---
### Author:  [@markschmucker](https://meta.discourse.org/u/markschmucker)
#### Post date: [28 בינואר, 2026, 5:41am UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/625 "2026-01-28T05:41:16Z")
We plan to allow users to change their email address on our main site (the SSO provider). We would like to update their email in Discourse at the same time, without them having to go to their Discourse preferences, and without them having to validate their new email with Discourse. What is the best way to implement this?
I experimented with updating their email like below, but that just added a **secondary** Discourse email which was pending validation. I want to change their **primary** Discourse email with no validation. Validation is performed by the main site.
```plaintext
curl -X PUT "https://discourse.example.com/u/$TARGET_USERNAME/preferences/email.json" \
-H "Api-Key: $DISCOURSE_API_KEY" \
-H "Api-Username: $DISCOURSE_USERNAME" \
-H "Content-Type: application/json" \
-d '{"email": "new-address@example.com"}'
```
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [28 בינואר, 2026, 8:23am UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/626 "2026-01-28T08:23:40Z")
Did you enable the `auth_overrides_email` site setting?
> [@Sync DiscourseConnect user data with the sync\_sso route](https://meta.discourse.org/t/sync-discourseconnect-user-data-with-the-sync-sso-route/84398):
>
> Single Sign On can be used to handle Discourse user authentication from a separate site. The [Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso)](https://meta.discourse.org/t/official-single-sign-on-for-discourse-sso/13045) topic has details about how to implement [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) . The Problem With [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) , Discourse users will be created or updated when they login to Discourse from your external website. What it doesn’t handle is when you need to create or update Discourse users without having them login to your site. For sites that are using…
---
### Author:  [@markschmucker](https://meta.discourse.org/u/markschmucker)
#### Post date: [28 בינואר, 2026, 10:25am UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/627 "2026-01-28T10:25:28Z")
Not sure how I overlooked that- I did see the overrides for avatar, name, and username. Thanks!
---
### Author:  [@markschmucker](https://meta.discourse.org/u/markschmucker)
#### Post date: [27 במאי, 2026, 3:47am UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/628 "2026-05-27T03:47:22Z")
Some users are reporting when they log on with SSO, they get an error: “The change you wanted was rejected.”. I have `auth_overrides_email` set, as well as name, username, and avatar. I suspect the rejected change is for one of those, but I’m having a hard time finding useful info in the logs. I’ve looked at /logs- sometimes there is a “Primary email is already taken”, but I can’t find why Discourse is apparently trying to create a new user instead of authorizing the user with that email. I’ve also grepped in `/var/discourse/shared/standalone/log/rails`, but didn’t find anything enlightening.
[Previous page](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045.md?page=2)