jeffnolan's comments

HVAC, appliances, and “other” are the major drivers for electricity consumption in commercial and residential customer bases. In industry, 50% of the power is consumed by machinery.

I wonder if the decrease in lighting (driven by LEDs) is offset by the increase in electronics in commercial and residential sites.

It's not a password store, SSO services like OneLogin are federated services that authenticate users with encrypted tokens. In a SAML transaction, or with OAuth, a username/password combination is never exchanged. How is this better, aside from user experience? For starters, the ability to disrupt access benefits from a single point rather than having to change passwords in every app. It also benefits from relying on a credential from a directory service that can then be used to provision access within the target application, which means you can have more granular role-based or dynamic access based on metadata like time of day or geolocation.

it's a semantic argument. You are not storing passwords in an SSO service, but it is passing tokens to authenticate access based on the asserting/relying relationship between IdP and app. The reason I say it is semantic is that while you are not storing passwords, you are sitting on a trove of access credentials. What is different about an SSO app that is of huge value is that cutting off access is not a function of changing passwords at the app level.

I think we agree on all the major points here, but I would not diminish the significance based on the fact that OneLogin is not a password vault.