Gabe with DO here. That's a bummer. I hope our support team is able to get your access restored. If you get stuck feel free email me: gabe@
Thank you Gabe, I sent you an email.
How to lose access of our your servers on DigitalOcean
21–30 of 32 posts
Re: How to lose access of our your servers on DigitalOcean
#22Re: How to lose access of our your servers on DigitalOcean
#23At least you've learned a good lesson here. If you want ownership of an account, you need ownership of the email you use. And do a hard separation between personal and work services. Also, it sucks the hoops you're going through, but it's good they resist common social engineering tactics like they are. Good on them. Maybe suck up to a sys admin to re-instate the email for a day if support goes nowhere.
They did everything to confirm my Identity and prevent social engineering tactics which is exactly what I expected from the company. But I feel like they don't have an internal process to solve this issue, I haven't anything back for the last 8 hours..
To be fair - for a standard account, not hearing back for 8 hours wouldn’t concern me too much
Re: How to lose access of our your servers on DigitalOcean
#24Earlier quoted context omitted.
They did everything to confirm my Identity and prevent social engineering tactics which is exactly what I expected from the company. But I feel like they don't have an internal process to solve this issue, I haven't anything back for the last 8 hours..
To be fair - for a standard account, not hearing back for 8 hours wouldn’t concern me too much
For sure the SLO for standard account is 24hrs.
Re: How to lose access of our your servers on DigitalOcean
#25This happened to me with Tailscale, but because my GitHub name changed. It was quite confusing at first.
Re: How to lose access of our your servers on DigitalOcean
#26Earlier quoted context omitted.
Thank you Gabe, I sent you an email.
Received. I confirmed the team is working the issue. Stay tuned.
Thank you very much for helping on this, Much Appreciated!
I would love to see improvements on the "Social Authentication" process, making the third party ID as primary identifier, instead of the email.
Re: How to lose access of our your servers on DigitalOcean
#27Earlier quoted context omitted.
Received. I confirmed the team is working the issue. Stay tuned.
Thank you very much for helping on this, Much Appreciated! I would love to see improvements on the "Social Authentication" process, making the third party ID as primary identifier, instead of the email.
I hear you. I’ll talk to the team about how we can do better.
Re: How to lose access of our your servers on DigitalOcean
#28simply don't use sso.. it's full of these kinds of edge cases.
Thankfully we don't "login with facebook" anymore either
Re: How to lose access of our your servers on DigitalOcean
#29Earlier quoted context omitted.
I love Digital Ocean, don't get me wrong. Im just sharing the Bad experience with the "Social Authentication" flow and how long it is taking to solve a simple problem. This also a heads up for anyone using GitHub as the authentication method.
It's definitely not a simple problem though. Anyone can claim they own your account. And it would be bone-headed to make the re-verification process easy.
And now the company admin, or if the domain for sale again, can take over his account
Re: How to lose access of our your servers on DigitalOcean
#30Earlier quoted context omitted.
Thank you very much for helping on this, Much Appreciated! I would love to see improvements on the "Social Authentication" process, making the third party ID as primary identifier, instead of the email.
I hear you. I’ll talk to the team about how we can do better.
I work in the public service sector. When we're architecting OAuth2/OIDC integrations we specify using a unique identifier like a guid or some otherwise immutable id as the federation id. This way other attributes that may be ephemeral can change at will. It's not always easy determining this but it's worth it.