5 ms·

Agreed. SAML even makes sense for solo dev.

by vermorel 6y ago

harha 6y ago
could you elaborate further with use-cases?
- tiffanyh 6y ago
  Not having to create separate usernames and passwords with yet another service (GitHub)
  - m01 6y ago
    With GitHub (cloud version) specifically it doesn't (currently) work that way, you still need a "normal" GitHub username and password, and you do the organisational SAML login in regular intervals when trying to access that org's resources. I'm not aware of this being a widespread way of doing SAML, but I guess it supports certain use-cases (like keeping a GitHub identity despite switching jobs/OSS projects). sources: * https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on https://help.github.com/en/github/setting-up-and-managing-or... * https://help.github.com/en/github/authenticating-to-github/about-authentication-with-saml-single-sign-on https://help.github.com/en/github/authenticating-to-github/a... [edit: formatting]
- eastbayjake 6y ago
  As a business customer of a SaaS product, being able to revoke any employee's access to the SaaS tool if they are terminated. (Imagine how hard this would be for e.g. the SaaS tool your company uses to view financial reporting if it required every user at your company to create their own username/password. If you wanted to prevent someone from "going rogue" during termination, you would need to have an admin remove their account access prior to termination -- and do it on every SaaS product that person used. With SSO you revoke their access and everything gets locked out. Source: Watching an alcoholic CTO get fired by the board and taking the startup's hosted Mongo database hostage
  - jfkebwjsbx 6y ago
    I agree, but I think the GP was asking about use cases for a solo dev.
    - eastbayjake 6y ago
      Good clarification! If you're a solo dev who wants to sell your side project to any company >500 people, SAML integration is tablestakes. If you're a solo dev who needs to secure your hobby project on the public internet, it's like bringing a Space Shuttle engine to a knife fight.
      - jholman 6y ago
        If I was in a knife fight, and my buddy showed up and just hit the guy I was fighting with a SSME, I would be totally impressed and also grateful.
nogabebop23 6y ago
So you care a lot about this, but not $4/month care?
- dfabulich 6y ago
  SAML is an enterprise feature; it's $21/user/month.
- Spivak 6y ago
  Right but $5/month/service is where it starts to add up. Unless you're managing hundreds of users across a bunch of disparate services the value/cost doesn't work out in your favor.

Agreed. SAML even makes sense for solo dev.

harha 6y ago

could you elaborate further with use-cases?

tiffanyh 6y ago
Not having to create separate usernames and passwords with yet another service (GitHub)
- m01 6y ago
  With GitHub (cloud version) specifically it doesn't (currently) work that way, you still need a "normal" GitHub username and password, and you do the organisational SAML login in regular intervals when trying to access that org's resources. I'm not aware of this being a widespread way of doing SAML, but I guess it supports certain use-cases (like keeping a GitHub identity despite switching jobs/OSS projects). sources: * https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on https://help.github.com/en/github/setting-up-and-managing-or... * https://help.github.com/en/github/authenticating-to-github/about-authentication-with-saml-single-sign-on https://help.github.com/en/github/authenticating-to-github/a... [edit: formatting]
eastbayjake 6y ago
As a business customer of a SaaS product, being able to revoke any employee's access to the SaaS tool if they are terminated. (Imagine how hard this would be for e.g. the SaaS tool your company uses to view financial reporting if it required every user at your company to create their own username/password. If you wanted to prevent someone from "going rogue" during termination, you would need to have an admin remove their account access prior to termination -- and do it on every SaaS product that person used. With SSO you revoke their access and everything gets locked out. Source: Watching an alcoholic CTO get fired by the board and taking the startup's hosted Mongo database hostage
- jfkebwjsbx 6y ago
  I agree, but I think the GP was asking about use cases for a solo dev.
  - eastbayjake 6y ago
    Good clarification! If you're a solo dev who wants to sell your side project to any company >500 people, SAML integration is tablestakes. If you're a solo dev who needs to secure your hobby project on the public internet, it's like bringing a Space Shuttle engine to a knife fight.
    - jholman 6y ago
      If I was in a knife fight, and my buddy showed up and just hit the guy I was fighting with a SSME, I would be totally impressed and also grateful.

nogabebop23 6y ago

So you care a lot about this, but not $4/month care?

dfabulich 6y ago
SAML is an enterprise feature; it's $21/user/month.
Spivak 6y ago
Right but $5/month/service is where it starts to add up. Unless you're managing hundreds of users across a bunch of disparate services the value/cost doesn't work out in your favor.