feat/login-via-gmail #21
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a crazy workaround for CRS' Login via Gmail only feature. I said crazy because it's a complicated thing to do in the app now. With this, I am thinking of switching to Javascript extension client, but would still reuse some of my endpoints.
Basically, I set up a Selenium-based browser to open the CRS website in which you can login via UP email. Once you have logged in into CRS, Selenium will harvest cookies of the successful attempt of the login, notify the popup that it has successfully harvested the cookies, then finally feed those cookies into the scraper session. At this point, we're essentially scraping the authenticated version of the site!
Docker, on the other hand, doesn't support Selenium-based browser popup, so Login via Gmail option will now be useless when
docker-compose up --buildis used. I am hoping CRS would set theusernameandpasswordagain.For now, I'm gonna find more alternatives.