views:

979

answers:

5

Heroku seems great, but most non-trivial applications require authentication, and conventional authentication schemes require an SSL connection, and it's impossible to get https://your_app_name.com (you can only get https://your_app_name.heroku.com).

So if you're using Heroku, is it that:

  1. You don't mind directing users to another domain (seems pretty bad)
  2. You don't mind foregoing SSL for authentication (seems really bad)
  3. Your app doesn't require authentication

Edit: In your answer, please select one of the above options.

A: 

You can use a custom domain name in Heroku. This is not included in the free account though. Also Heroku makes it dead simple to deploy Ruby on Rails apps. Deploying a Ruby on Rails application on a cheap hosting provider that only gives you limited if any shell access can be a nightmare. Not mention Heroku's server already preconfigured to optimize Ruby on Rails code, likewise scaling up is just a matter of sliding a scale on the user interface.

So which one of the options in my question is it? I guess you don't care about SSL?
Horace Loeb
A: 

With Heroku you can use custom domain names (in the free version too). Scaling is easy, very easy, and they are making it better and better (i'm testing memcached and work like a charm, delayed job, the backup system and the git integration are great too). The only problem for me, as you wrote is the SSL...

How is the lack of SSL not a total show-stopper? Can you give an example of an application that doesn't require it?
Horace Loeb
OpenID doesn't require ssl on the client to be secure. So, you could use it.
BaroqueBobcat
+8  A: 

Hey, it's James from Heroku. The inability to use SSL with a custom domain is a problem shared by all multi-tenant platforms, due to a fundamental issue with the SSL protocol. A solution is in the works, we'll post details as soon we've finalized the plan.

James at Heroku
+16  A: 

This is now a moot point. According to the documentation (http://docs.heroku.com/ssl), Heroku now allows custom domains to have SSL through two different mechanisms.

There are several SSL options from which to choose, ranging from free to $100/month. Each option has its pros and cons, but they all add SSL capability.

Sixty4Bit
Yup, this is fixed -- Heroku is amazing
Horace Loeb
you forgot to mention that ssl on heroku costs $100/month
feydr
There are several SSL options to choose from. $100/month is the most expensive while free is the least expensive. Each option has its pros and cons, but they all add SSL capability.
Sixty4Bit
+2  A: 

I'm using Twitter's OAuth for authentication on my apps (via twitter-auth).

Generic OpenID or even Facebook Connect would work just as well, as each of these handle the sensitive bits of authentication on somebody else's server.

Authlogic is an authentication gem that has has plugins for each of these methods.

However, SSL is now fully supported on Heroku, if you're willing to pay a price that reflects the difficulty in getting SSL to work in a multi-tenant environment.

phloopy