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

Simplify master password requesting #70

Open
kelson42 opened this issue Jan 5, 2021 · 2 comments
Open

Simplify master password requesting #70

kelson42 opened this issue Jan 5, 2021 · 2 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@kelson42
Copy link
Contributor

kelson42 commented Jan 5, 2021

Currently this is a bit cumbersome, but we could make this request easier via Slack. see https://www.workato.com/the-connector/2017/10/approval-slack-workflows-draft/ and https://api.slack.com/messaging/interactivity.

@kelson42 kelson42 added enhancement New feature or request good first issue Good for newcomers labels Jan 5, 2021
@rgaudin
Copy link
Member

rgaudin commented Jan 5, 2021

Can you elaborate more on this? What's master password requesting and what does Slack have to do with it?

My understanding is that you would like to not input the master password when you create a new repo and instead set up a Slack App that would ask you on Slack so you just have to click a button. Is that it?

If so, then this issue's title is misleading as you want a new slack-integration feature. This would obviously be optional.

I fail to see how this can be worth the effort. In the documented workflow, usage of the master password should be quite rare. Doing this would require writing, maintaining and deploying (and keeping running) a new tool for this sole purpose, with the additional worry that this would hold access to your master bitwarden account.

@kelson42
Copy link
Contributor Author

kelson42 commented Jan 5, 2021

Operations requesting the master password are not that rare, in particular with #57.

For now each time this is needed we have to run the Docker container with a dedicated mode and from someone having this password. This is clear and properly documented but cumbersome because it cuts any effort needed this in two clearly different operations and these two operations (in our case) have to be run by two different users.

The workflow I propose is that each time needed the backup system contacts the master user via Slack to enter the master password. That way:

  • The flows don't have to be splitted in two, it is only one flow which is waiting the master password
  • This is far less cumbersome for the master user (and the backup responsible)
  • Assuming the Slack channel is secure, we don't loose in security

There is as well a bit of meta level, where I believe we could use such approach to solve a few tasks which are at the same time hard to fully automatize but recurring enough that this is quite time consuming to do that manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants