# Login with SSO option does not exchange SSL certificates

**URL:** https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664
**Category:** Self-hosting
**Tags:** hosting
**Created:** [2017年七月23日 10:18 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664 "2017-07-23T10:18:56Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![vishal\_vr](https://avatars.discourse-cdn.com/v4/letter/v/7ba0ec/32.png) [@vishal\_vr](https://meta.discourse.org/u/vishal_vr)
#### Post date: [2017年七月23日 10:18 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/1 "2017-07-23T10:18:56Z")

</div>

I have a main domain hosted on Firebase, which runs the actual website of our business. Then installed Discourse platform hosted in another sub domain but on a different hosting platform. Discourse forum was edited and works just fine, however when i enable login with SSO with the links, the domain hosted on Firebase does not excahnge SSL certificates with the Discourse platform. Kindly help me how to enable SSO login in this case where Firebase does not send SSL certificates outside its domain. Or what should be enabled for the SSO to work fine.

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [2017年七月23日 23:08 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/2 "2017-07-23T23:08:43Z")

</div>

I can’t understand what you’re asking for. “Exchange SSL certificates” is not a common term of art. Perhaps screenshots or other objective observations of what you’re seeing, and how that differs from what you expect to see, might clarify the situation?

---

<div class="post-metadata">

### Author: ![vishal\_vr](https://avatars.discourse-cdn.com/v4/letter/v/7ba0ec/32.png) [@vishal\_vr](https://meta.discourse.org/u/vishal_vr)
#### Post date: [2017年七月24日 08:35 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/3 "2017-07-24T08:35:42Z")

</div>

![](https://global.discourse-cdn.com/meta/original/3X/3/7/37f7fcb9aceb7ab0e03d33caeb06745a24999956.JPG)

It says the certificate is only vaild for “[firebaseapp.com](http://firebaseapp.com) or \*.firebaseapp.com”

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [2017年七月24日 09:13 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/4 "2017-07-24T09:13:43Z")

</div>

> [@vishal\_vr](#):
>
> It says the certificate is only vaild for “[firebaseapp.com](http://firebaseapp.com) or \*.firebaseapp.com”

That screenshot is very helpful. As you identified, the problem is that the certificate only covers `*.firebaseapp.com`, while you’re trying to access `www.<something>.firebaseapp.com`. The thing with “wildcard certificates” (which this is) is that the `*` only covers one “level” of name – so it would match `<something>.firebaseapp.com`, but not what you’re using.

Your options are:

1. connect using `<something>.firebaseapp.com`, or
2. use a different domain entirely (and obtain a suitable SSL certificate).

---

<div class="post-metadata">

### Author: ![vishal\_vr](https://avatars.discourse-cdn.com/v4/letter/v/7ba0ec/32.png) [@vishal\_vr](https://meta.discourse.org/u/vishal_vr)
#### Post date: [2017年七月25日 18:55 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/5 "2017-07-25T18:55:17Z")

</div>

Thank you very much, can you elaborate or provide pointers to resources on your suggestion. Sorry for the trouble as i am new to web development and computer science.

> options : 1. connect using \<something\>.firebaseapp.com

Do i need to install discourse on Firebase again? As of now it is on DigitalOcean as it was simple. Or is it just the hosting of the domain?

---

<div class="post-metadata">

### Author: ![elijah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elijah/32/104055_2.png) [@elijah](https://meta.discourse.org/u/elijah)
#### Post date: [2017年七月25日 21:21 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/6 "2017-07-25T21:21:25Z")

</div>

Not knowing anything about Firebase, I don’t know if you need to install it again there. What you need is a hostname of the form `DNSLABELWITHOUTDOTS.firebaseapp.com` or an SSL cert for the hostname you’ve chosen (`www.crowdpouch-lb3dbd.firebaseapp.com`). Edit your app.yml file for either change and then `launcher rebuild app`.

(You might find it easier to just get a free Let’s Encrypt certificate, which the scripts can do for you, if app.yml is so configured.)

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [2017年七月25日 22:39 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/7 "2017-07-25T22:39:50Z")

</div>

You’ll need to talk to Firebase support about what your options are. We can’t provide support for their setup.

---

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [2017年七月26日 04:03 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/8 "2017-07-26T04:03:12Z")

</div>

It’s not a Firebase issue, it’s a configuration issue on Discourse side.  
TS said Discourse was running elsewhere. This happens when Discourse triggers the SSO.

@vishal_vr you just need to remove the `www.` in front of the URL in your [Discourse SSO](https://meta.discourse.org/t/13045?silent=true) settings.

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [2017年七月26日 04:07 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/9 "2017-07-26T04:07:39Z")

</div>

How is “Firebird is presenting a certificate that doesn’t match the hostname” a Discourse configuration issue?

---

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [2017年七月26日 09:37 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/10 "2017-07-26T09:37:41Z")

</div>

The website is [https://crowdpouch-b3dbd.firebaseapp.com/](https://crowdpouch-b3dbd.firebaseapp.com/) without www and it is working fine.

In the screenshot you can see that the URL that is showing the error, is the SSO callback URL.  
That URL must have been the result of a redirect from Discourse.

So I figured that removing the www in the [Discourse SSO](https://meta.discourse.org/t/13045?silent=true) configuration would solve this issue.

---

<div class="post-metadata">

### Author: ![elijah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elijah/32/104055_2.png) [@elijah](https://meta.discourse.org/u/elijah)
#### Post date: [2017年七月26日 15:57 UTC](https://meta.discourse.org/t/login-with-sso-option-does-not-exchange-ssl-certificates/66664/11 "2017-07-26T15:57:28Z")

</div>

Yes. You need to use the same hostname consistently. Discourse won’t be adding the “www”, that’s something else, possibly leftover from some [www.example.com](http://www.example.com) type placeholder.
