Non-HTTP auth

[geoffharcourt]

Is the Harry's team open to building some very simple auth with a mechanism rather than HTTP? I'm proposing to do email/password auth with http://github.com/thoughtbot/clearance, which is much lower overhead than Devise, but still allows for email/password auth for multiple users.

I'm going to end up doing this for our own deployment of Cronut, so wanted to check.

[danielschwartz]

Ill let @blahblahblah- make the final call on this but we're definitely open to a non-http auth solution. I might propose a Devise solution rather than clearance because of our experience with two factor auth and devise -- very easy to setup and we love two factor. I can't promise we would get to it that soon but if timing is an issue we'd absolutely be open to implementing the two factor solution if you implement the standard Devise solution.

[blahblahblah-]

I don't really have much of a preference either way, but I do agree with @danielschwartz that it'll be easy for us to implement it with two-factor authentication as well as role-based authorization using CanCan since there may be a need for separate access levels for read vs. write.

[werkshy]

If I had my druthers we'd have a way to use a central directory for apps like this, e.g. LDAP via AWS Directory Services or Jumpcloud.