# SSO Redirect Problem

**URL:** <https://meta.discourse.org/t/sso-redirect-problem/59044>\
**Category:** Bug\
**Tags:** pr-welcome\
**Created:** [14. März 2017 um 01:08 UTC](https://meta.discourse.org/t/sso-redirect-problem/59044 "2017-03-14T01:08:30Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![thepenguinmaster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thepenguinmaster/32/121140_2.png) [@thepenguinmaster](https://meta.discourse.org/u/thepenguinmaster)\
**Post date:** [14. März 2017 um 01:08 UTC](https://meta.discourse.org/t/sso-redirect-problem/59044/1 "2017-03-14T01:08:30Z")

</div>

I am working with [Discourse SSO](https://meta.discourse.org/t/13045?silent=true) authentication and running into a problem with redirects. I am able to successfully login and everything works great, until the user logs in using GitHub or Google.

What seems to be happening is our site redirects to Discourse, Discourse accepts the SSO request, allows user to select GitHub, and redirects to GitHub. The user logs in, and is redirected to Discourse, but the last redirect back to our service is never completed. Discourse forgot my encoded request to Discourse? Why would Discourse not complete the redirect back to my service after GitHub or other login via OAuth?

I believe this may be a bug, but suspect I may be missing a header.

Any help would be appreciated!

Thank you,  
ThePenguinMaster

---

_[View the full topic](https://meta.discourse.org/t/sso-redirect-problem/59044)._