8000 Idea: accept TOTP/2FA/Security Answers via the web · Issue #6 · searls/fine-ants-app · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Idea: accept TOTP/2FA/Security Answers via the web #6

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

Open
searls opened this issue Aug 13, 2017 · 0 comments
Open

Idea: accept TOTP/2FA/Security Answers via the web #6

searls opened this issue Aug 13, 2017 · 0 comments

Comments

@searls
Copy link
Owner
searls commented Aug 13, 2017

What I'd like is to remove "watching the terminal" from the workflow:

  1. fine_ants scrapes and returns a 2FA question to answer
  2. fine_ants_app displays a UI prompting the user for the 2FA answer
  3. fine_ants_app returns the answer to fine_ants, which continues scraping

Challenges to this:

  • Currently, fine_ants uses stdin for this stuff and just blocks until it gets an answer.
  • Multiple web requests can't just block the main thread
  • Capybara/Selenium are really finicky and will lose their connection to a browser at the drop of a hat

Ideas:

Since this is a local/single-tenant app, we can get away with murder and do whatever we want. Like:

  1. Start up a separate long-running process that runs fine_ants and negotiates back and forth using stdout/stdin
  2. Run the fine_ants API in a separate long-lived thread so that we can poke at it over multiple requests
  3. hand-wavey actioncable idea

I think route 2 is actually desirable, because it would allow the app to recover gracefully if the scraper is ever broken in the main thread (which currently requires an app restart).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant
0