# SSO - "There is a problem with your account. Please contact the site's administrator."

**URL:** https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126
**Category:** SSO
**Created:** [6. April 2016 um 12:58 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126 "2016-04-06T12:58:18Z")
**Posts on this page:** 18
**Page:** 1

<div class="post-metadata">

### Author: ![programster](https://avatars.discourse-cdn.com/v4/letter/p/e68b1a/32.png) [@programster](https://meta.discourse.org/u/programster)
#### Post date: [6. April 2016 um 12:58 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/1 "2016-04-06T12:58:18Z")

</div>

I just setup SSO on my discourse forum that I deployed through docker using the latest “stable” version (1.5). To clarify, I have my own SSO service that I am using to log into discourse. I am not using Discourse as an SSO provider. I used the cviebrock/discourse-php PHP package in order to develop the SSO service to work with discourse.

Whenever I hit login, everything redirects okay, but I land on the discourse forum with the message:

> There is a problem with your account. Please contact the site’s administrator.

The address I land on is:

`http://discourse.mydomain.org/session/sso_login?sso=bm9uY2U9NzFiNGIzM2UxMGQxYWJiYzc1MGI3MDFjMzE4ZTQwZTMmZXh0ZXJuYWxfaWQ9NTcw&sig=a3250a90855912afdbeb13be004449df52f404934b0414de02444c0d9be812ad`

I tested messing with the signature or the sso and if I do that I get a blank page. I also tested plugging in an incorrect secret and got a different error message.

Has anyone else received this error message and know what I should do? Are there logs anywhere I can get more detailed information from?

---

<div class="post-metadata">

### Author: ![programster](https://avatars.discourse-cdn.com/v4/letter/p/e68b1a/32.png) [@programster](https://meta.discourse.org/u/programster)
#### Post date: [6. April 2016 um 13:23 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/2 "2016-04-06T13:23:34Z")

</div>

Nevermind, it was a stupid implementation error on my part. I had the code:

```
$extraParameters = array(
    'name' => $userEmail = $_SESSION['name']
);

```

which should have been:

```
$extraParameters = array(
    'name' => $_SESSION['name']
);

```

I don’t khow how to delete or close this post, but would be grateful if someone else would.

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [6. April 2016 um 16:31 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/4 "2016-04-06T16:31:59Z")

</div>

> [@programster](#):
>
> I don’t know how to delete or close this post, but would be grateful if someone else would.

You can’t on your own. Here, we recommend that you ask a moderator 😉

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [6. April 2016 um 21:39 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/5 "2016-04-06T21:39:07Z")

</div>

Hmm, how can we make the error message more useful in this case? Any ideas?

---

<div class="post-metadata">

### Author: ![aknudsen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aknudsen/32/115845_2.png) [@aknudsen](https://meta.discourse.org/u/aknudsen)
#### Post date: [24. Mai 2016 um 11:40 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/7 "2016-05-24T11:40:20Z")

</div>

No suggestions, but I agree it should be more descriptive!

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [24. Mai 2016 um 16:00 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/8 "2016-05-24T16:00:24Z")

</div>

@techapj can you add to your list, to look into this error message and any detail we can add to it at the time it occurs?

---

<div class="post-metadata">

### Author: ![emanuelet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/emanuelet/32/121710_2.png) [@emanuelet](https://meta.discourse.org/u/emanuelet)
#### Post date: [9. Juni 2016 um 01:53 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/9 "2016-06-09T01:53:58Z")

</div>

At the moment I have a user on my Discourse instance experiencing this issue. For the SSO I’m using the official Wordpress Plugin [GitHub - discourse/wp-discourse: WordPress plugin that lets you use Discourse as the community engine for a WordPress blog · GitHub](https://github.com/discourse/wp-discourse) version 0.7

---

<div class="post-metadata">

### Author: ![emanuelet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/emanuelet/32/121710_2.png) [@emanuelet](https://meta.discourse.org/u/emanuelet)
#### Post date: [15. Juni 2016 um 07:01 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/10 "2016-06-15T07:01:33Z")

</div>

and now I have a new one. I’m hosting Discourse version 1.5.2

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [27. August 2018 um 22:58 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/12 "2018-08-27T22:58:14Z")

</div>

Possibly, not sure if @techapj had a chance to look.

---

<div class="post-metadata">

### Author: ![techAPJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techapj/32/342990_2.png) [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [29. August 2018 um 00:08 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/14 "2018-08-29T00:08:29Z")

</div>

I didn’t had the chance to improve logging here yet. It’s on my low priority list.

> [@Emmanuel\_Straschnov](#):
>
> Where should I look in the meantime?

I recommend enabling `verbose sso logging` setting and debug logs.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [10. September 2018 um 21:12 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/16 "2018-09-10T21:12:25Z")

</div>

> [@Emmanuel\_Straschnov](#):
>
> We do have more and more cases about this and cannot help our users.

What do you see when ..

> [@techAPJ](#):
>
> I recommend enabling `verbose sso logging` setting and debug logs.

.. you follow the above advice and look in `/logs` via your web browser?

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [10. September 2018 um 22:06 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/18 "2018-09-10T22:06:00Z")

</div>

I don’t see any email field in that sso payload - make sure that the provider has an email on file for everyone.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [10. September 2018 um 22:11 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/19 "2018-09-10T22:11:50Z")

</div>

If the email is actually there (and not blank), perhaps that email address has been banned or blacklisted. Check your site settings and admin, logs, screened emails.

---

<div class="post-metadata">

### Author: ![comepasto](https://avatars.discourse-cdn.com/v4/letter/c/2acd7d/32.png) [@comepasto](https://meta.discourse.org/u/comepasto)
#### Post date: [4. Dezember 2018 um 09:18 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/21 "2018-12-04T09:18:59Z")

</div>

Hi,  
I found another wierd behavior to get this error. And it is very annoying. Documentation sais that the SSO has to urlEncode the values of the unsigned payload.

Ok, for example I map the value of **user.name** :

- Single string. Works fine
- String with ONE space. It can either be encoded with a **+** or **%20** (both are valid urlEncodings). Works fine
- String with TWO or MORE spaces. When they are encoded with a **+** , **ERROR**. With **%20** works fine.

One space encoded with a ‘+’ works but several ‘+’ don’t? And the logs do not raise any error about this.

I think this is worth mentioning in the SSO documentation.

Thank you

---

<div class="post-metadata">

### Author: ![vavalomi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vavalomi/32/105717_2.png) [@vavalomi](https://meta.discourse.org/u/vavalomi)
#### Post date: [14. Januar 2019 um 21:32 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/22 "2019-01-14T21:32:12Z")

</div>

This generic error shows up also when hitting the registration limit from the same ip - only saw the real reason after enabling verbose logging …

---

<div class="post-metadata">

### Author: ![William\_Entriken](https://avatars.discourse-cdn.com/v4/letter/w/a8b319/32.png) [@William\_Entriken](https://meta.discourse.org/u/William_Entriken)
#### Post date: [18. März 2019 um 13:47 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/23 "2019-03-18T13:47:41Z")

</div>

I now get this error with SSO. Possibly related to change an account’s email address from the WordPress side.

---

<div class="post-metadata">

### Author: ![William\_Entriken](https://avatars.discourse-cdn.com/v4/letter/w/a8b319/32.png) [@William\_Entriken](https://meta.discourse.org/u/William_Entriken)
#### Post date: [18. März 2019 um 13:56 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/24 "2019-03-18T13:56:15Z")

</div>

The solution for my problem was:

1. Admin → Settings → enable verbose SSO logging
2. Navigate to /logs on one screen while attempting to login on the other

This found the problem, then…

1. Delete existing account (non-sso) with the same email address
2. Reattempt SSO login

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [2. März 2024 um 06:50 UTC](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126/25 "2024-03-02T06:50:40Z")

</div>


