4 ms·

It’s much easier than ever before. You centralize identity to an IDP and require SAML or OAuth for applications. Then you manage it once. Typically you can get

It’s much easier than ever before. You centralize identity to an IDP and require SAML or OAuth for applications. Then you manage it once. Typically you can get rid of most of the password bullshit by adding MFA, with some exceptions. Unless you’re a DoD contractor or handling taxpayer data the came from the IRS on behalf of a client, MFA should meet or exceed compliance requirements.

deleted 4y ago
[deleted]
eastbound 4y ago
I’m a small company and the problem with SAML is that it requires the “enterprise” plan for each app. Slack goes from 0 to $11.75/month/user, Miro goes from $8 to $16. Then you have to pay for Okta (Isn’t it $15/u/m?) For a 5-person business it’s $1185 difference + $900 for Okta, and that doesn’t make me SOC2 compliant (There is a bunch of other requirements, secure access to physical offices, logs, etc.).
- ethanzh 4y ago
  sso.tax lists tons of examples of the price increases you’ve mentioned
  - eastbound 4y ago
    I love that! Needs to be more known, it’s like SSL certificates when LetsEncrypt didn’t exist. Edit: It has been posted 7 times in the last year.
- Spooky23 4y ago
  Usually it makes sense to use Google or Microsoft as an IDP vs Okta. Totally hear you re the cost, it depends on the risks you face. I’m in a bigger enterprise, but for me, no SSO, it is out in 95% of situations. In the exceptions we have, we require vaulted passwords. A breach would put me out of business, and identity is a key security control for many risks.
thayne 4y ago
Some customers require that your employees have to comply with their password requirements. Using an IdP means there is just one password to worry about, but you still might have to periodically change your password because some big customer has it in their contract. And then there are customers who have requirements about passwords, even though they are only going to be using an IDP anyway. It is probably because they have the same standard list of requirements that they give to everyone, and probably was copied from somewhere else, and you can usually contest it. But it is still a waste of time for everyone.

deleted 4y ago

[deleted]

eastbound 4y ago

I’m a small company and the problem with SAML is that it requires the “enterprise” plan for each app. Slack goes from 0 to $11.75/month/user, Miro goes from $8 to $16. Then you have to pay for Okta (Isn’t it $15/u/m?) For a 5-person business it’s $1185 difference + $900 for Okta, and that doesn’t make me SOC2 compliant (There is a bunch of other requirements, secure access to physical offices, logs, etc.).

ethanzh 4y ago
sso.tax lists tons of examples of the price increases you’ve mentioned
- eastbound 4y ago
  I love that! Needs to be more known, it’s like SSL certificates when LetsEncrypt didn’t exist. Edit: It has been posted 7 times in the last year.
Spooky23 4y ago
Usually it makes sense to use Google or Microsoft as an IDP vs Okta. Totally hear you re the cost, it depends on the risks you face. I’m in a bigger enterprise, but for me, no SSO, it is out in 95% of situations. In the exceptions we have, we require vaulted passwords. A breach would put me out of business, and identity is a key security control for many risks.

thayne 4y ago

Some customers require that your employees have to comply with their password requirements. Using an IdP means there is just one password to worry about, but you still might have to periodically change your password because some big customer has it in their contract. And then there are customers who have requirements about passwords, even though they are only going to be using an IDP anyway. It is probably because they have the same standard list of requirements that they give to everyone, and probably was copied from somewhere else, and you can usually contest it. But it is still a waste of time for everyone.