# Inserimento di commenti tramite SSO

**URL:** https://meta.discourse.org/t/embedding-comments-via-sso/95537
**Category:** SSO
**Created:** [24 Agosto 2018, 4:49am UTC](https://meta.discourse.org/t/embedding-comments-via-sso/95537 "2018-08-24T04:49:06Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Lukas\_Majercak](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lukas_majercak/32/109154_2.png) [@Lukas\_Majercak](https://meta.discourse.org/u/Lukas_Majercak)
#### Post date: [24 Agosto 2018, 4:49am UTC](https://meta.discourse.org/t/embedding-comments-via-sso/95537/1 "2018-08-24T04:49:06Z")

</div>

Hi there!

I recently setup a discourse instance ([https://arbitio-community.co.uk](https://arbitio-community.co.uk)) and configured SSO via my Django app.  
I am trying to do the following:

1. user logs in to my django app
2. I automatically do /session/sso login for discourse in the background
3. embed topics on the django app

I came across [https://meta.discourse.org/t/sso-login-from-main-site-backend/37933](https://meta.discourse.org/t/sso-login-from-main-site-backend/37933), which suggests to add an embed tag for discourse/session/sso, but I’m seeing issues there:

 ![image](https://global.discourse-cdn.com/meta/original/3X/5/1/5100ce15a1820ca3f2cc9c9198eec41109950d2c.png)

My discourse is set up to be https only, so I’m not sure why does it seems to be redirecting to HTTP.  
Any ideas why this is, or different approaches to achieve this workflow?

Thanks!

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [24 Agosto 2018, 11:12am UTC](https://meta.discourse.org/t/embedding-comments-via-sso/95537/2 "2018-08-24T11:12:10Z")

</div>

Is force https is set, are you doing some kind of reverse proxy? If so, that’s probably the problem.

---

<div class="post-metadata">

### Author: ![Lukas\_Majercak](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lukas_majercak/32/109154_2.png) [@Lukas\_Majercak](https://meta.discourse.org/u/Lukas_Majercak)
#### Post date: [24 Agosto 2018, 4:35pm UTC](https://meta.discourse.org/t/embedding-comments-via-sso/95537/3 "2018-08-24T16:35:22Z")

</div>

Not that I know, no. It’s running on a single EC2 instance, without any proxy/balancer in front of it.

---

<div class="post-metadata">

### Author: ![Lukas\_Majercak](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lukas_majercak/32/109154_2.png) [@Lukas\_Majercak](https://meta.discourse.org/u/Lukas_Majercak)
#### Post date: [26 Agosto 2018, 3:35am UTC](https://meta.discourse.org/t/embedding-comments-via-sso/95537/4 "2018-08-26T03:35:10Z")

</div>

Are there any verbose logs I could enable to debug this?

---

<div class="post-metadata">

### Author: ![Lukas\_Majercak](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lukas_majercak/32/109154_2.png) [@Lukas\_Majercak](https://meta.discourse.org/u/Lukas_Majercak)
#### Post date: [26 Agosto 2018, 9:10pm UTC](https://meta.discourse.org/t/embedding-comments-via-sso/95537/5 "2018-08-26T21:10:04Z")

</div>

Found the issue, I was returning a non-HTTPS discourse redirect /session/sso\_login URL from my server.