Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I suggest see if you can access things. If so, find out who is responsible. Does the client know you shouldnt have access anymore? If not whose job was it to tell them?
When I left a company who manages airports it was up to me to turn in my credentials. If I didnt do that I risked never being allowed on that airport anymore. -
@Codex404
the accounts are still active, and are full admin accounts. I am sure I can still do everything. There were no new accounts added. They just didn't update the passwords (at least).
and the clients know that i've left. some of them handle this sort of issue inhouse, and they should have already, for the other the company where i worked handled access and security. -
@rutee07
nothing ... really nothing. I have no issues with any of the companies involved so i dont want to make trouble for any of them.
i'll just stand back and be sad that they weren't as ... proffesional as i would have expected them to
also, i did message a friend that still works there to handle the issue -
when your code is a mess but everything work out in the end
When you keep getting +1s on a rant you posted a month ago.
Go big or go home.
Really curious:
After what amount of time after leaving your previous job, where you were deeply involved with client side infrastructure and deployment, would you expect the credentials to stop working / be changed ?
I should state that the credentials are not service accounts, but also not distinct for every dev / devops.
I might also add that the clients involved are courier services, service providers and ... Oh yeah ... A financial institution
Also everyone is based in the EU, so GDPR and all ...
question
ethics
professionalism
rant