6 ms·
I'm largely in favor of SSO, but it's not without its downsides, going beyond capital costs: SSO can also be implemented in a way that introduces an onerous lat
by dswalter 2y ago
I'm largely in favor of SSO, but it's not without its downsides, going beyond capital costs: SSO can also be implemented in a way that introduces an onerous latency tax when using services.
- dijit 2y agoBecause of proxying? SSO (SAML/OAUTH2) are usually implemented with a token, like normal auth. There should be no penalty aside from login.
- scott_w 2y agoI’m not sure about that beyond login. That said, Okta has gotten reasonably good when you have a Yubikey, so I’ve stopped complaining about it.
- justin_oaks 2y ago> SSO can also be implemented in a way Unless you're more specific, I'm going to assume that that "way" is the wrong way. Initial login shouldn't add more latency than a couple web redirects. The authentication token/assertion should be validated only once and not be needed until it expires or the user logs out.