> If a feature of an open core product can be provided by the community, it's not valuable enough to gate behind an enterprise wall. I don't think that holds a

> If a feature of an open core product can be provided by the community, it's not valuable enough to gate behind an enterprise wall. I don't think that holds as a general rule, because there's no conceptual moat preventing any feature from being reimplemented by a third party with sufficient motivation and resources. "The community" sometimes includes larger companies who build an open-source re-implementation of a smaller company's closed-source enterprise features. At best, they do this purely for self-serving reasons; and at worst, for anti-competitive ones. > Nor is it a bad thing when a community implementation competes with the enterprise implementation Personally I don't think it is reasonable to expect the maintainers of this project to maintain two separate OIDC implementations, one of which they didn't write in-house. They may have different naming conventions, config options, etc. Sounds like a support and maintenance nightmare.