# Issues in Integrating SSO in Discourse
**URL:** https://meta.discourse.org/t/issues-in-integrating-sso-in-discourse/49533
**Category:** Support
**Created:** [01.Сентябрь.2016 06:24:12 UTC](https://meta.discourse.org/t/issues-in-integrating-sso-in-discourse/49533 "2016-09-01T06:24:12Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Hammad\_Abbasi](https://meta.discourse.org/u/Hammad_Abbasi)
#### Post date: [01.Сентябрь.2016 06:24:12 UTC](https://meta.discourse.org/t/issues-in-integrating-sso-in-discourse/49533/1 "2016-09-01T06:24:12Z")
HI,
I have followed this guide to enable SSO Integration with my app [Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso)](https://meta.discourse.org/t/official-single-sign-on-for-discourse/13045)
Local Logins are now now disabled and Discourse correctly redirects user to SSO Url however I am getting 500 error when my application redirects back to
http://discourse\_site/session/sso\_login?sso=payload&sig=sig
(It looks like the page doesn’t exist? What am i missing here ? Please advice )
P.S I installed discourse image using docker so its using latest release
**EDIT: I have enabled Logging and now its showing “Bad Signature for Payload”**
Thanks in Advance.
---
### Author:  [@Hammad\_Abbasi](https://meta.discourse.org/u/Hammad_Abbasi)
#### Post date: [01.Сентябрь.2016 09:46:03 UTC](https://meta.discourse.org/t/issues-in-integrating-sso-in-discourse/49533/2 "2016-09-01T09:46:03Z")
It turns out that the culprit was encoding scheme, SSO is now working like a charm
---
### Author:  [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [01.Сентябрь.2016 17:38:55 UTC](https://meta.discourse.org/t/issues-in-integrating-sso-in-discourse/49533/3 "2016-09-01T17:38:55Z")