Future Consideration 2FA for VPN
Good morning from the not so sunny UK!
We have several ER7206 (and a few ER605) based at different clients sites, and we would like to have the ability to add 2 factor authentication to the VPN setup please. This feature nowadays is a must have for cyber assurance purposes, so it seems daft to have to implement another VPN solution when you have 99% of it already built into the router. It's just missing that last option!
Even the OpenVPN server built into the ER7206 doesn't appear to have the option for 2FA, and to my knowledge this is standard option for the OpenVPN server.
This router fulfills all of our requirements and the Omada ecosystem as a whole is fantastic, it's just this one drawback!
Many thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Morning!
Me again.
Thought I would come back on this as there's been a lot of discussion around this, and what staggers me at the moment is the attitude of "Well no one else does it (even though they do), so why should we?".
Surely the mindset of "Let's look at implementing this much requested feature for our growing base of customers, and get a step ahead of our competition and prove to them that we are serious about our business products", would work much better than "Nah, cba tbh".
Just a thought.........
- Copy Link
- Report Inappropriate Content
Hi @DaveMcDave
Thanks for posting in our business forum.
DaveMcDave wrote
Morning!
Me again.
Thought I would come back on this as there's been a lot of discussion around this, and what staggers me at the moment is the attitude of "Well no one else does it (even though they do), so why should we?".
Surely the mindset of "Let's look at implementing this much requested feature for our growing base of customers, and get a step ahead of our competition and prove to them that we are serious about our business products", would work much better than "Nah, cba tbh".
Just a thought.........
There are many more features and RFC grows. So we'd keep every feature/protocol integrated?
This was brought to the dev's attention as the label says. We don't have specific details or an ETA for this implementation.
Not until the EdgarFonseca chimed in and shared his experience with Draytek. No one else provided a concrete and helpful competitor's move. Others' replies in a way that "I need it".
BTW, @EdgarFonseca, thanks for the information. I am convinced that this might be something the dev can try.
Pretty clear in the reply that we need some information on the use case, scenario, size of your network, and other vendors' implementation. And it is the information we need for an evaluation and a report (for the dev and PM, they need it). Getting to know the information of a feature request is a common ground I had with the dev in the last phone call discussion on some feature requests.
As mentioned above, it is clear that this should be something that needs to be done in the future and it has been brought to the dev's attention. (This is not a guarantee if there is a hardware limitation. Simply based on the use case and feedback. It is supposed to be done.)
I will wait for the message from the dev if they have a plan or a roadmap about this and notify you and others about this feature. Will not comment on this as it is enough for the moment.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 13
Views: 1956
Replies: 33