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

Implement optional login #14

Closed
redshiftzero opened this issue Sep 11, 2018 · 1 comment
Closed

Implement optional login #14

redshiftzero opened this issue Sep 11, 2018 · 1 comment

Comments

@redshiftzero
Copy link
Contributor

Requirements:

  • Users should be able to open and use the SecureDrop client application without authenticating to the server, i.e. when disconnected from the network entirely. In this scenario, they are unable to sync, and unable to reply to sources, and the corresponding UI elements should be greyed out / inactive.

  • When requesting or sending new content to the server, they'll need to get an API token, by providing their username, password, and 2FA token. We need a UI form that allows them to do this. The actual login functionality would be provided by the SDK's API.authenticate method.

Related: a common complaint from our journalist user research is that there are too many different logins, passphrases, etc., so if we can ease the burden, then that would be good from the user's perspective. Recall in order to get to the SecureDrop client application, they need to also know both the login for the Qubes user, and the FDE passphrase for the workstation (these can be the same).

@ntoll
Copy link
Contributor

ntoll commented Oct 11, 2018

This was fixed by #29

legoktm pushed a commit that referenced this issue Dec 11, 2023
Adds lock file and requirements files as required for packaging
legoktm pushed a commit that referenced this issue Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants