two separate Okta instances. It was a coin toss as to which one you’d need for any given service
oh, and a third internally developed federated login service for other stuff
90 day expiry for all of the above passwords
two different corporate IM systems, again coin toss depending on what team you’re working with
nannyware everywhere. Open Performance Monitor and watch network activity spike anytime you move your mouse or hit a key
an internally developed secure document system used by an international division that we were instructed to never ever use. We were told by IT that it “does something to the PC at a hardware level if you install the reader and open a document” which would cause a PC to be banned from the network until we get it replaced. Sounds hyperbolic, but plausible given the rest of the mess.
required a mobile authenticator app for some of the above services, yet the company expected that us grunts use our personal devices for this purpose.
all of the above and more, yet we were encouraged to use any cloud hosted password manager of our choosing.
This makes sense only if you’re rolling your own silicon, and it depends on the application. I could see this as an alternative to a scalar DSP core or to provide more flexible high speed interfaces. The unspoken cost is going to be adding another proprietary set of tooling in the BSP for your chip.