# 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 Abril, 2016 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:** 1\
**Showing post:** 21

<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 Diciembre, 2018 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

---

_[View the full topic](https://meta.discourse.org/t/sso-there-is-a-problem-with-your-account-please-contact-the-sites-administrator/42126)._