Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: 2 Factor on launchpad with lockout on other services #5

finechap opened this issue Nov 2, 2017 · 3 comments


Copy link

commented Nov 2, 2017

I understand it's impossible to put 2 factor login over every service individually.
But certainly a good boost to my security would be a feature along the lines of:

  • 2 factor on launchpad
  • an optional lockout on other services (eg FTP, SSH) that's only unlocked by a successful 2 factor login.
  • the lockout is selectable per service.
  • Time window for unlock is selectable eg default 2 hrs but can be set to 12 for letting an FTP job run over night.
  • Multiuser would be great but I'd happily take it on admin only.
  • If you did do multiuser could use that to solve problems where you need automated access to services. Eg Create a new user that doesn't use 2 factor but only has read only rights to needed files. This login could be used by a regular FTP backup service.
  • If you want to get really fancy could have a learning mode like fortification, where for a short period you go into 'full access' mode. Start your FTP connection. After that launchpad get shows you the IPs that accessed in full mode and you can select the ones to whitelist for the longer running 'limited mode'.
  • 2 factor reset would be via email so (as per now) admin email is still the keys to the castle. 2 factor was never a silver bullet but a boost non the less.

@msaladna msaladna added this to the 3.1 milestone Nov 2, 2017


This comment has been minimized.

Copy link

commented Dec 17, 2018

Depends upon #11

@msaladna msaladna added the depends label Dec 17, 2018


This comment has been minimized.

Copy link

commented Mar 11, 2019

3.1 is next on the list. Open a ticket within you panel so I can track this. A link back to this works or "dfkm24qwd", something to internally track.


This comment has been minimized.

Copy link

commented Mar 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.