# Inlogfout bij het gebruik van Discourse als identiteitsprovider (SSO, DiscourseConnect)

**URL:** <https://meta.discourse.org/t/login-error-while-trying-to-use-discourse-as-an-identity-provider-sso-discourseconnect/266603>\
**Category:** SSO\
**Created:** [30 mei 2023 om 13:28 UTC](https://meta.discourse.org/t/login-error-while-trying-to-use-discourse-as-an-identity-provider-sso-discourseconnect/266603 "2023-05-30T13:28:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ygramoel](https://avatars.discourse-cdn.com/v4/letter/y/74df32/32.png) [@ygramoel](https://meta.discourse.org/u/ygramoel)\
**Post date:** [30 mei 2023 om 15:45 UTC](https://meta.discourse.org/t/login-error-while-trying-to-use-discourse-as-an-identity-provider-sso-discourseconnect/266603/2 "2023-05-30T15:45:35Z")

</div>

One step further: if I turn on verbose loggin for [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true), I do get an error in the logs:

![image](https://global.discourse-cdn.com/meta/optimized/4X/3/4/a/34a67ebc64f104f8f8096d7cf9b0a2bf51abdb7a_2_690x71.png)

```plaintext
Verbose SSO log: Signature parse error Bad signature for payload sso: bm9uY2U9YklKeEU1WWw2OFhjSkJydGlwSU15UTRZeVlMeWd6ZzQyUU9mOFo0SWF5QSZyZXR1cm5fc3NvX3VybD1odHRwczovL2VtYmVldGxlLmNvbS8jYWNjb3VudA= 

```

One notable point is that the payload mentioned in the log is not URL-encoded (note the ‘=’ at the end) and is missing the second ‘=’ of the URL-encoded data (note the repeated `%3D` at the end of the original payload).

---

_[View the full topic](https://meta.discourse.org/t/login-error-while-trying-to-use-discourse-as-an-identity-provider-sso-discourseconnect/266603)._
