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: Support for Password-Protected Sites #18

Open
sakher opened this issue Mar 25, 2024 · 1 comment
Open

Feature Request: Support for Password-Protected Sites #18

sakher opened this issue Mar 25, 2024 · 1 comment

Comments

@sakher
Copy link

sakher commented Mar 25, 2024

Problem Description

Many valuable web resources require authentication, limiting the ability of "Papeer" to access and scrape these sites. Users frequently encounter password-protected pages, making it challenging to include these resources in their e-reader compatible formats. Current functionality does not support a way to authenticate against these sites directly through "Papeer."

Proposed Solution

Introduce functionality within "Papeer" to allow users to provide authentication details (e.g., username and password, API keys, session cookies) that can be used to log in to password-protected sites before scraping. This could be implemented in several ways:

  • Command Line Arguments: Allow users to pass authentication credentials as arguments when invoking "Papeer."
  • Configuration File: Enable users to store authentication details securely in a configuration file "Papeer" reads from.
  • Interactive Prompt: When encountering a password-protected site, "Papeer" could prompt the user to enter their credentials interactively, with an option to save these for future sessions.

Additional Context

  • Ensuring security and privacy of the stored credentials is paramount. Consideration should be given to encrypting the stored credentials if they are saved on disk.
  • This feature would significantly enhance "Papeer's" utility by expanding the range of accessible content for users, making it a more versatile tool for e-reader content preparation.

Potential Challenges

  • Handling different authentication mechanisms (basic auth, OAuth, form-based login, etc.) might require a flexible implementation.
  • Security concerns around storing and handling user credentials.

I believe this feature would be a valuable addition to "Papeer" and would greatly appreciate the team's consideration in implementing it. Thank you for your work on making "Papeer" such a useful tool for the community!

@sakher
Copy link
Author

sakher commented Mar 25, 2024

Created a branch to add cookies support - can't push a PR it seems.

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