So, authentication on Discourse seems like mostly a solved problem since you can offload it to an external provider, but I’d love for Discourse to have a two-factor option for local authentication. It seems relatively uncomplicated to bolt-on support for TOTP via Google Authenticator—for example, here’s a Google Authenticator add-on implementation in PHP for Roundcube. Right, right, apples and oranges, php and ruby, webmail and forum, but the libraries are all there and it’d definitely make me happy to see a two-factor option.
I’ll bump this just once, and then let it go. Would love for quick TOTP integration, but I understand that this might not be the time.
Would like to see this as well, I’ve recently gotten obsessed with two-factoring all my online accounts. And Authy is amazing, by the way.
For the record we are 100% for this feature, its just a matter of time. Too strapped for it now.
I wonder if we can get 2 factor auth for version 1.0?
No, definitely not. Sorry.
I would like this feature. Hopefully by 1.1.
Simplest way of pushing a feature forward in the schedule is contributing a PR
Giving this a bump because I would really like to see this feature as well.
If I had the skills I would submit something back to the project code wise to help move this along but I do not.
The first forums software to have this feature easily out of the box is the one I am likely going to be going with. I hope this is the one that has it first in all honesty as this seems to be the best designed software I have seen yet for forums.
My audience demands 2FA for all such things and sadly it appears I will be forced to use bbPress (really, really, awful) because it has support for Authy via a WordPress plugin at the moment.
If I may suggest something to keep in mind; Authy isn’t free e.g.: https://www.authy.com/pricing I did some research and found that Github built their own two-factor authentication system but it is NOT open source or usable by anyone but them (I was a little surprised at first but maybe they have good reason for that, idk).
My point is that it may be wise to build it from scratch(ish) and into the core instead of relying on costly third parties. Here is a good example of one called Authlogic that is built on Ruby and MIT licensed: https://github.com/binarylogic/authlogic (see also: http://rdoc.info/github/binarylogic/authlogic).
Just a suggestion but please keep in mind that any third party isn’t going to be free and stuff like that really adds up for admins and discourages people from using Discourse for that very reason.
Peace to all.
Any future for this?
We want this, but do not have it slotted yet.
Oh, ok. I would love to see it sometime in the near future.
Reviving this topic a bit—I recently got exposed to Duo Security’s super cool 2FA push authentication when we started rolling it out at Ars for staff, and I quickly decided I wanted to use it myself. I slapped it onto my self-hosted Roundcube install and am now using it on my ssh gateway box (via PAM integration—neat!!).
While TOTP-type 2FA would be great for normal users, the option to require 2FA for admins and mods should absolutely be a high priority. Duo is free for up to 10 users, and a Duo plugin for Discourse with the option of only requiring it for Admins/Mods would be awesome.
@sam and @codinghorror, I know you guys are busy, but this would be pretty damn cool. I’m willing to offer a bounty on it if you guys code for contributions
I like 2FA too. I’d like to work on this feature. However, we are so close to announce 1.2 so I think it’s better to develop it for the next release.
It makes me when people use “we” to talk about Discourse releases.
YubiKey or at least Google Authenticator support would be really great!!!
By the way: Has anyone some experience by SSO integration with services who does already support this? Something like clavid.ch?
Thanks!
Definitely still waving the flag for Duo. It’s just slick as hell.
(They have a ruby library for fast integration! Quality awesome coders like @sam and @eviltrout could probably bang this out in an afternoon!!)
I just wish I could invent more afternoons
https://github.com/discourse/discourse/pull/3282
The process is:
- A
user
goes to the profile page. - The
user
opens the two factor authentication setting page.
- It only shows up if the admin allows it.
- The
user
scans or input the secret into the devices.
- most likely the Google Authenticator
- I am not familiar with other apps or Yubikey…
- When the user wants to login:
- The
user
enters its credentials andlogin
. - The modal changes, the
user
needs to enter the two factor authentication code, thenlogin
.
For devs:
- If the otp login is required for the user, only assign the session to him.
[WIP] FEATURE: Add support for two factor authentication. by erickguan · Pull Request #3282 · discourse/discourse · GitHub - then the helper in the session controller requires the verification.
[WIP] FEATURE: Add support for two factor authentication. by erickguan · Pull Request #3282 · discourse/discourse · GitHub - In the preference page, the qr code is downloaded as needed.
[WIP] FEATURE: Add support for two factor authentication. by erickguan · Pull Request #3282 · discourse/discourse · GitHub - There is no rate limit.
- OTP code can be within the two windows. The interval is
30s
.30s | now | 30s
[WIP] FEATURE: Add support for two factor authentication. by erickguan · Pull Request #3282 · discourse/discourse · GitHub