# Discourse como provedor de SSO: "sso secret" vs. "sso provider secrets"
**URL:** https://meta.discourse.org/t/discourse-as-sso-provider-sso-secret-vs-sso-provider-secrets/100678
**Category:** Bug
**Created:** [Outubro 28, 2018, 1:35pm UTC](https://meta.discourse.org/t/discourse-as-sso-provider-sso-secret-vs-sso-provider-secrets/100678 "2018-10-28T13:35:04Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@jack2](https://meta.discourse.org/u/jack2)
#### Post date: [Outubro 28, 2018, 1:35pm UTC](https://meta.discourse.org/t/discourse-as-sso-provider-sso-secret-vs-sso-provider-secrets/100678/1 "2018-10-28T13:35:04Z")
My site SSO has been broken since the introduction of the `sso provider secrets` setting. To fix it, I needed to move my sso secret from the `sso secret` setting to the `sso provider secrets` setting.
So, as far as I can tell, the `sso secret` setting has been replaced by the `sso provider secrets` setting with no backward compatibility. Am I right?
If I am, then a UI bug remains: in the `enable sso provider` setting, “…requires sso\_secret to be set” should be replaced by “…requires sso\_provider\_secrets to be set”
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [Outubro 30, 2018, 6:49am UTC](https://meta.discourse.org/t/discourse-as-sso-provider-sso-secret-vs-sso-provider-secrets/100678/2 "2018-10-30T06:49:52Z")
“sso provider secrets” is only there IF you are using Discourse as an SSO endpoint. If you SSO implementation is NOT discourse you do not need to fill anything there.
> [@jack2](#):
>
> So, as far as I can tell, the `sso secret` setting has been replaced by the `sso provider secrets` setting with no backward compatibility. Am I right?
Not this is not the case
Can you please upgrade to latest ASAP and let us know if the issue remains. sso provider secrets should be blank for you UNLESS you are using Discourse as an auth provider for another Discourse site.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [Outubro 30, 2018, 8:40am UTC](https://meta.discourse.org/t/discourse-as-sso-provider-sso-secret-vs-sso-provider-secrets/100678/3 "2018-10-30T08:40:11Z")
We do have a [migration](https://github.com/discourse/discourse/blob/23ae2023efa94666eeaba5c7cfe0c1801ac92653/db/migrate/20181005084357_add_sso_provider_secrets_to_site_settings.rb) that copies the `sso secret` into the `sso provider secrets` site setting so I’m curious to know why yours wasn’t copied over?
---
### Author:  [@maja](https://meta.discourse.org/u/maja)
#### Post date: [Outubro 30, 2018, 9:14am UTC](https://meta.discourse.org/t/discourse-as-sso-provider-sso-secret-vs-sso-provider-secrets/100678/4 "2018-10-30T09:14:51Z")
> [@jack2](#):
>
> in the `enable sso provider` setting, “…requires sso\_secret to be set” should be replaced by “…requires sso\_provider\_secrets to be set”
This was outdated indeed after sso\_provider\_secrets site setting was introduced. I have updated the text in [FIX: sso provider copyedit · discourse/discourse@5485248 · GitHub](https://github.com/discourse/discourse/commit/5485248fbe1265b46483f97dbe20e2e8a62e48fd)
---
### Author:  [@jack2](https://meta.discourse.org/u/jack2)
#### Post date: [Novembro 1, 2018, 11:15am UTC](https://meta.discourse.org/t/discourse-as-sso-provider-sso-secret-vs-sso-provider-secrets/100678/5 "2018-11-01T11:15:34Z")
Sorry to be late on this.
@sam, I am using Discourse as an auth provider for another Discourse site.
@zogstrip, how can I help you identify why the migration didn’t work for me?