3 ms·

SSO probably involving SAML tied to a central “source of auth truth” like LDAP or G Suite or an AD/office365. when someone leaves you kill them in 1 place and a

SSO probably involving SAML tied to a central “source of auth truth” like LDAP or G Suite or an AD/office365. when someone leaves you kill them in 1 place and access is removed everywhere. bonus points if you tie in a higher layer 3rd party auth API offering like onelogin/centrify/etc that your internal apps can use. edit to add costs: a small company can do this for 3-5 bucks/user/month. that kind of cost is doable for a small shop, and worth it.

bsder 7y ago
> you kill them in 1 place and access is removed everywhere But how do I now take over their repositories and email, for example? > edit to add costs: a small company can do this for 3-5 bucks/user/month. that kind of cost is doable for a small shop, and worth it. Do you have a concrete reference? I really don't want to use a Google-based system. Microsoft could be an answer even if I reflexively cringe at that--they at least seem to be able to deal with businesses properly. I'm really not averse to paying money for this, but it needs to be seamless enough that we can use it from the CEO to the receptionist.