|
|
|
|
|
by fishtoaster
1724 days ago
|
|
This is absolutely perfect for a use case that I've seen a lot: shared test accounts. Eg our app connects to external service X, so we have a staging account set up such that the staging version of our app can operate. But service X values security and requires 2fa on all accounts. This is really annoying, especially if service X is expensive and charges per seat. We don't want to pay for a seat for all of our developers just for our test account, so we share credentials, which is a pain in the ass with required 2fa. A slack-based shared 2fa account would be perfect for this. I'd be pretty hesitant to use something like this for accounts I consider sensitive, though, because A. It's too easy to accidentally add the wrong person to slack, and ideally not everyone at the company has access to all accounts anyway, and B. It's putting more trust into a third party (tfa.one) than I'd be comfortable with, given how new it is. But again, perfect for our test accounts, and cheap enough that I don't even need to think about it. |
|