Why make a core security feature, SSO, so expensive? #11734
Unanswered
kijaco
asked this question in
Other Feature Feedback, Questions, & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
If GitHub claims to “take your security seriously”, then SSO should be available as a feature that is either:
part of the core product, or
an optional paid extra for a reasonable delta, or
attached to a price tier, but with a reasonably small gap between the non-SSO tier and SSO tiers.
It is a best practice and good security posture to enable SSO at your organization if you have over five employees. Why are companies, including GitHub (Microsoft), making it a part of "enterprise" plan and charging an arm and a leg for it ($4 per u/m vs. $21 per u/m, a 425% increase). SSO is not only a large company solution.
I outlined some possible solutions for GitHub above and urge them to consider making a change if they really want to show they value our security.
Beta Was this translation helpful? Give feedback.
All reactions