# SSO client link giving error 500
**URL:** https://meta.discourse.org/t/sso-client-link-giving-error-500/86854
**Category:** WordPress
**Created:** [May 5, 2018, 11:03pm UTC](https://meta.discourse.org/t/sso-client-link-giving-error-500/86854 "2018-05-05T23:03:43Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Sami\_Syed](https://meta.discourse.org/u/Sami_Syed)
#### Post date: [May 5, 2018, 11:03pm UTC](https://meta.discourse.org/t/sso-client-link-giving-error-500/86854/1 "2018-05-05T23:03:43Z")
**I have done the following to setup my word press as a SSO client:**
On wordpress
1. added all fields in the “connection” tab
2. added by secret key
3.
On discourse
1. enable SSO provider
2. add SSO secret key
Although, when i try and sign in I get the following screen.
How could I fix this?
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [May 6, 2018, 1:07am UTC](https://meta.discourse.org/t/sso-client-link-giving-error-500/86854/2 "2018-05-06T01:07:48Z")
> [@Sami\_Syed](#):
>
> How could I fix this?
My guess is that the problem is because of what you are asking about here:
> [@Edited htaccess and now im getting discourse sso expired error](https://meta.discourse.org/t/edited-htaccess-and-now-im-getting-discourse-sso-expired-error/86848):
>
> I am using my wordpress site to function as an SSO client. Meaning Discourse authenticates all users (logins, registrations, etc…). After editing my htaccess file to increase my wordpress site speed. I noticed that the following error started to appear when I try and login “discourse\_sso\_error=expired\_nonce”. I looked through the forum and found out that the issue is probably because of the htaccess file. Although, I want to know what exactly I should remove from it. So that I can keep my site…
Could you try using the default WordPress `.htaccess` configuration and see if you are still getting an error?
---
### Author:  [@Sami\_Syed](https://meta.discourse.org/u/Sami_Syed)
#### Post date: [May 6, 2018, 1:14am UTC](https://meta.discourse.org/t/sso-client-link-giving-error-500/86854/3 "2018-05-06T01:14:19Z")
Instead I just reverted back to a wordpress backup from 2 days ago (with the original htaccess file). Although, the problem was still there. But when I cleared all my cache. cookies and history, it started to work again.
Kind of a weird situation but im glad I sorted it out.
---
### Author:  [@Sami\_Syed](https://meta.discourse.org/u/Sami_Syed)
#### Post date: [May 6, 2018, 1:15am UTC](https://meta.discourse.org/t/sso-client-link-giving-error-500/86854/4 "2018-05-06T01:15:24Z")
Do you think the wp optimize plugin could have anything to do with this?
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [May 6, 2018, 1:21am UTC](https://meta.discourse.org/t/sso-client-link-giving-error-500/86854/5 "2018-05-06T01:21:46Z")
> [@Sami\_Syed](#):
>
> Do you think the wp optimize plugin could have anything to do with this?
I don’t know. If you can figure that out, and why that is the case, please let us know. We can’t get into a lot of WordPress development on this forum, but it’s good to know about conflicts between the [WP Discourse](https://github.com/discourse/wp-discourse) plugin and any other WordPress plugins. It makes debugging issues a lot easier.
---
### Author:  [@nylen](https://meta.discourse.org/u/nylen)
#### Post date: [July 23, 2019, 7:12am UTC](https://meta.discourse.org/t/sso-client-link-giving-error-500/86854/6 "2019-07-23T07:12:38Z")
For anyone else experiencing this error, I fixed it by filling in the `sso provider secrets` setting for the client domain name:
In the Discourse code, when this secret is not set, the call to `OpenSSL::HMAC.hexdigest` fails with the following error in the logs:
> TypeError (no implicit conversion of nil into String) /var/www/discourse/lib/single\_sign\_on.rb:114:in `hexdigest’
Here is the relevant code path:
- [discourse/lib/single\_sign\_on\_provider.rb at f364317625ee273d1e8983faa271831db912953b · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/f3643176/lib/single_sign_on_provider.rb#L21-L34)
- [discourse/lib/single\_sign\_on.rb at f364317625ee273d1e8983faa271831db912953b · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/f3643176/lib/single_sign_on.rb#L69)
- [discourse/lib/single\_sign\_on.rb at f364317625ee273d1e8983faa271831db912953b · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/f3643176/lib/single_sign_on.rb#L112)
This error message should definitely be improved! \_Edit: and it has been - see [https://meta.discourse.org/t/confusing-unpolished-error-message-when-using-discourse-as-sso-provider/123762\_](https://meta.discourse.org/t/confusing-unpolished-error-message-when-using-discourse-as-sso-provider/123762_)
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [August 22, 2019, 7:12am UTC](https://meta.discourse.org/t/sso-client-link-giving-error-500/86854/7 "2019-08-22T07:12:47Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.