4 ms·

withholding enterprise features from free versions isn't the problem, the problem is charging extortionate rates for an important security feature. > "Decouple

• ozim 1y ago
  Problem is lots of SSO implementation will be dealing with some arrogant architects claiming you know nothing and their semi broken SAML is something you should implement for them for free - repeat for 100 times for each customer having their own way of breaking the spec or using something crooked. It is getting better with Entra P2 or Okta as it is couple of minutes to configure if you use good framework in your projects. But the tax was because of what I wrote about in first place.
  • tetha 1y ago
    This is why at work, we're encouraging and recommending to use some kind of SSO, but we're basing our cost off of the customers IDP. Some "green" IDP like O365 OIDC, Okta, Entra and such are usually included without extra cost (and will be self-service soon, too). Some "yellow" - usually SAML - IDPs come at a fixed fee. We know them, we know they are weird, but we can deal with it. Other things are flagged as red and call in hourly billed projects and recurring maintenance fees. Like, one customer has an in-house developed SAML IDP written in PHP a decade ago or so. I want our customers to use SSO, but that's a level of jank I'm not supporting for free.