Join Log in
Score:0
nicholaswmin avatar Server

White-labelling with SSL on Heroku

us flag
nicholaswmin

Our app runs on Heroku with a domain pointed to it at example.com.

We now want to offer a whitelabel solution to our users so companies can use our product under their own custom domain.

For example instead of https://example.com, they would access our product under their own domain, i.e https://bar.com.

What we currently do is the following:

  • Ask the user what domain they want to whitelabel under (i.e bar.com)
  • We add bar.com in our Heroku app domains and give them the DNS target provided by Heroku.
  • We ask them to add the DNS target provided by Heroku when the domain was added, as CNAME record in their DNS.

The problem we have now has to do with SSL. Our SSL certs on Heroku are for *.example.com, not for *.bar.com therefore visiting acme.com would generate an SSL error.

What we could do is ask from our users their SSL certificates for acme.com, create a new SSL endpoint under our Heroku app and use that SSL endpoint when adding their domain to the app.

The problem is that, obviously, we cannot ask our users to give us the SSL certificates of their websites.

Is there an alternative to the above solution?

37
0 + 0
ssl
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.