![]() In order to do that, we have expanded our investment in engineering, design, quality assurance and product resources to address community feedback around improving reliability, usability and capabilities of the platform and will report progress back to the community on a monthly basis. I’d like to reinforce that we believe in the power of the community and will continue to strengthen it. ![]() This will ensure complete transparency for the community around how these types of decisions are made. Accordingly, we will be able to continue to expand our identity management features to keep up with functionality requests while ensuring that the workspaces who leverage those capabilities for commercial purposes help with the evolution of Rocket.Chat.Īs a resource and commitment to the community, we’re also putting together a public stewardship document (link to be shared soon) that details the operating principles used to decide how features and capabilities are split between the community edition and the enterprise version of Rocket.Chat. It will enable us to keep improving quality and reliability, and to enhance support for community features. This change will allow our team to support the advanced identity management features more effectively. It’s worth noting that we’ll continue our commitment to long time community contributors, open source non-profits, and people who do good things around the world - if you’re running a non-commercial initiative on Rocket.Chat, as always, just reach out. ![]() All others require a paid license, a complex configuration or a third party integration. It is important to note that, even after this release, Rocket.Chat will still be the only major open source communications platform to include any LDAP feature in its community edition. Here’s a full description of the feature set available with each edition and a Frequently Answered Questions (FAQ). The community edition LDAP feature will allow workspaces to connect to an LDAP server and import user names and identifiers, but additional capabilities such as syncing extended user attributes, managing group & team assignments and background synchronization will require an enterprise license. In our (tentative) September 27th release, selected advanced functionalities (role mappings, background syncs, etc) of those features will be implemented only in the Rocket.Chat enterprise edition, while all the basic functionalities of LDAP, SAML, Social Logins and Custom OAuth will remain available for use and extension in the community edition. Our team has recently completed a refactoring of all identity management integrations including LDAP features, SAML integration and advanced Oauth capabilities. To keep pace, we’ve invested in growing the size of the team to ensure that we can improve the quality and capabilities of the open source community edition and paid versions of the platform. The community of Rocket.Chat users has continued to grow rapidly during 2021. Existing contributors, non-profit, or “do good” organizations should contact us for concession discount and free programs. We are doing this to better support and service those who depend on these advanced features, and to be able to invest back into our ever-growing community. This is unlikely to affect current users of SAML, Oauth, or Custom Oauth, as most of the basic features remain in the Community Edition. Rocket.Chat has started refactoring code that will have select advanced identity management features implemented only in Enterprise Edition. ![]() NOTE: This message has been edited on September 14th for clarity incorporating constructive suggestions from our supportive community.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |