Earlier quoted context omitted.
This is the real reason there's an SSO tax. It costs to support SSO, the customers who want SSO should pay for that cost.
There are plenty of folks who setup SSO with open source projects without a support contract. Why should they have to pay for it with other software?
An admittedly wandering defense of the SSO tax
81–90 of 99 posts
Re: An admittedly wandering defense of the SSO tax
#82Earlier quoted context omitted.
Because the engineers of the other software chose not to work for free?
I'm not saying they shouldn't be compensated, just that justifying the SSO tax due to the support burden is pearl clutching.
Re: An admittedly wandering defense of the SSO tax
#83Earlier quoted context omitted.
Yes! We don't charge for SSO, but thankfully we've only had our largest customers ask for it -- and every time it required significant back-and-forth to get it set up. Basically every time somebody comes in with a new IdP, I have to go stand up my own instance so I can figure out what weird combination of options will make it work, because I'm convinced nobody actually understands SAML.
Nobody understands SAML because it doesn’t really exist. It’s not so much a standard as a bag of standard parts from which a protocol can be assembled. It’s possible for two implementations to be fully compliant and yet incompatible. PS: the single most common developer error is assuming the SAML configuration is static and has a single certificate somewhere. The modern approach is to get all configuration from a met…
I die Not make this experience. The specs exist and are detailled. I'm Not convinced your Last sentence ist true.
Re: An admittedly wandering defense of the SSO tax
#84As someone who deals with application support, another big reason is SSO is such a support nightmare. No one wanted to touch SSO tickets because of how frustrating they were to deal with. People wouldn't follow the instructions. Microsoft/Google moved something in their portal and we didn't know so instructions were useless. Microsoft/Google would be having issues and we got tickets because they were still working un…
This is the real reason there's an SSO tax. It costs to support SSO, the customers who want SSO should pay for that cost.
Re: An admittedly wandering defense of the SSO tax
#85This car with no seat belts, no airbags, and no ABS is just price discrimination! Strangely, no one seems interested in celebrating the implied discount for not having safety.
This is a solid objection that I hadn't considered before! Why isn't SAML SSO mandated (either literally or my convention)? Practically speaking, as someone who spends all day trying to convince developers to implement SAML SSO, I really wish this were the case :) I think in practice, software vendors correctly assess that relatively few of their prospective customers actually care. If many small / price sensitive co…
I used OIDC for my internal sites to integrate with our corporate SSO provider. Why would I need to use saml instead?
Re: An admittedly wandering defense of the SSO tax
#86Earlier quoted context omitted.
This is the real reason there's an SSO tax. It costs to support SSO, the customers who want SSO should pay for that cost.
There’s a cost to support non sso authentication to.
SSO issues usually takes 10 or 20 times longer to sort out any issue.
Re: An admittedly wandering defense of the SSO tax
#87Earlier quoted context omitted.
I was lead engineer for a startup. By virtue of being the most flexible in my day-to-day, I ran front line for most of the customer support issues. SSO issues took exponentially longer than nearly every other support issue and accounted for well over 50% of our support efforts. We didn’t really feel like there was much we could do about it either. Most of it came down to the fact that the user of our application was…
Yeah but does that require any expertise to solve? It’s a bunch of meaningless arcana, for which the other party pays well. Seems like a fair deal. Someday you might get big enough where it’s minions talking to minions, or so big that people simply accept no customer service as the status quo.
There are basically three major issues that require a bit of seniority to support:
* it’s an auth controlling system so mistakes can mean significant data breaches.
* there’s shared responsibility between provider and customer for configuration. Further, there are a lot of possible configurations to consider.
* the concept behind SSO is largely simple, but the implementation can be very complex. It’s almost always specific to your auth system and controls.
Re: An admittedly wandering defense of the SSO tax
#88Re: An admittedly wandering defense of the SSO tax
#89Re: An admittedly wandering defense of the SSO tax
#90This car with no seat belts, no airbags, and no ABS is just price discrimination! Strangely, no one seems interested in celebrating the implied discount for not having safety.
I wouldn't celebrate taking those cars away from people.