# Community Edition limitations **URL:** \ **Category:** Search Guard\ **Created:** [May 8, 2018, 4:34pm UTC](https://forum.search-guard.com/t/community-edition-limitations/905 "2018-05-08T16:34:10Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Matteo\_Cusmai](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@Matteo\_Cusmai](https://forum.search-guard.com/u/Matteo_Cusmai)\ **Post date:** [May 8, 2018, 4:34pm UTC](https://forum.search-guard.com/t/community-edition-limitations/905/1 "2018-05-08T16:34:10Z")
- Search Guard and Elasticsearch version 6.2.4 - JVM version and operating system version 1.8 Hi all, I am newbie on search guard, and I need to understand the limitation of community edition, so I have some questions: - is the code on github under apache license? if so, is the code of community edition? - which is the best way to be sure that I am using the community edition? - I have compiled the plugins from github on my PC, and then I have installed the plugins on elastic and kibana, can I suppose that I am using the community edition of the plugins? Thanks a lot, Matteo. ---
**Author:** ![jkressin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/jkressin/32/9_2.png) [@jkressin](https://forum.search-guard.com/u/jkressin)\ **Post date:** [May 8, 2018, 4:51pm UTC](https://forum.search-guard.com/t/community-edition-limitations/905/2 "2018-05-08T16:51:57Z")
Hi, the code in the search-guard repository is the code for the Community Edition and Apache2 licensed: > **[GitHub - floragunncom/search-guard: Search Guard Plugin - Security for...](https://github.com/floragunncom/search-guard)** > > Search Guard Plugin - Security for Elasticsearch. Contribute to floragunncom/search-guard development by creating an account on GitHub. [https://github.com/floragunncom/search-guard/blob/master/LICENSE](https://github.com/floragunncom/search-guard/blob/master/LICENSE) The code for the Enterprise and Compliance Edition is under a commercial license and can be found here: > **[GitHub - floragunncom/search-guard-enterprise-modules: Search Guard...](https://github.com/floragunncom/search-guard-enterprise-modules)** > > Search Guard Enterprise Modules - LDAP/AD/SAML/Kerberos etc - GitHub - floragunncom/search-guard-enterprise-modules: Search Guard Enterprise Modules - LDAP/AD/SAML/Kerberos etc [https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE](https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE) So as long as you are using the search-guard repo only, you are only using Apach2 licensed code and the Community Edition. We have also integrated a switch which will turn off all enterprise features, so you can be absolutely sure you only use the Community edition: > **[Community Edition](https://docs.search-guard.com/latest/search-guard-community-edition)** > > The Search Guard Community Edition provides TLS encryption and index-level permissions on REST and transport for free. The Kibana Plugin is Apache2 licensed as well. So, judging from what you wrote, you are indeed using the Community Edition of Search Guard. > **···** > > On Tuesday, May 8, 2018 at 6:34:10 PM UTC+2, Matteo Cusmai wrote: > > > - Search Guard and Elasticsearch version 6.2.4 > > > - JVM version and operating system version 1.8 > > > > > > Hi all, > > > I am newbie on search guard, and I need to understand the limitation of community edition, so I have some questions: > > > - is the code on github under apache license? if so, is the code of community edition? > > - which is the best way to be sure that I am using the community edition? > > - I have compiled the plugins from github on my PC, and then I have installed the plugins on elastic and kibana, can I suppose that I am using the community edition of the plugins? > > Thanks a lot, > > > Matteo. ---
**Author:** ![Matteo\_Cusmai](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@Matteo\_Cusmai](https://forum.search-guard.com/u/Matteo_Cusmai)\ **Post date:** [May 14, 2018, 2:08pm UTC](https://forum.search-guard.com/t/community-edition-limitations/905/3 "2018-05-14T14:08:35Z")
Hi Jochen, thanks for the quick reply. I have changed the date of my virtual machine in order to make expired the trial license, and when I open kibana I see the following message: ### Search Guard System Status [Back](http://ubuntu-16-elk:5601/app/searchguard-configuration#/) The Search Guard license key is not valid for this cluster. Reason: - License is expired How I can delete the trial license since I, up to now, am not using the enterprise capabilities. Thanks a lot, Matteo. > **···** > > On Tue, May 8, 2018 at 6:51 PM, Jochen Kressin [jkressin@floragunn.com](mailto:jkressin@floragunn.com) wrote: > > > Hi, > > > > > > the code in the search-guard repository is the code for the Community Edition and Apache2 licensed: > > > [https://github.com/floragunncom/search-guard](https://github.com/floragunncom/search-guard) > > > [https://github.com/floragunncom/search-guard/blob/master/LICENSE](https://github.com/floragunncom/search-guard/blob/master/LICENSE) > > > > > > The code for the Enterprise and Compliance Edition is under a commercial license and can be found here: > > > > > > [https://github.com/floragunncom/search-guard-enterprise-modules](https://github.com/floragunncom/search-guard-enterprise-modules) > > > [https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE](https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE) > > > > So as long as you are using the search-guard repo only, you are only using Apach2 licensed code and the Community Edition. > > > > > > We have also integrated a switch which will turn off all enterprise features, so you can be absolutely sure you only use the Community edition: > > > > > > [https://docs.search-guard.com/latest/search-guard-community-edition](https://docs.search-guard.com/latest/search-guard-community-edition) > > > > > > The Kibana Plugin is Apache2 licensed as well. > > > > > > So, judging from what you wrote, you are indeed using the Community Edition of Search Guard. > > > On Tuesday, May 8, 2018 at 6:34:10 PM UTC+2, Matteo Cusmai wrote: > > > > > - Search Guard and Elasticsearch version 6.2.4 > > > > - JVM version and operating system version 1.8 > > > > > > > > Hi all, > > > > I am newbie on search guard, and I need to understand the limitation of community edition, so I have some questions: > > > > - is the code on github under apache license? if so, is the code of community edition? > > > - which is the best way to be sure that I am using the community edition? > > > - I have compiled the plugins from github on my PC, and then I have installed the plugins on elastic and kibana, can I suppose that I am using the community edition of the plugins? > > > Thanks a lot, > > > > Matteo. > > > – > > > > You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group. > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [search-guard+unsubscribe@googlegroups.com](mailto:search-guard+unsubscribe@googlegroups.com). > > > > To post to this group, send email to [search-guard@googlegroups.com](mailto:search-guard@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/9f1ac54c-cdd7-4168-bc11-46aaf7da7c86%40googlegroups.com](https://groups.google.com/d/msgid/search-guard/9f1ac54c-cdd7-4168-bc11-46aaf7da7c86%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > Matteo Cusmai ---
**Author:** ![jkressin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/jkressin/32/9_2.png) [@jkressin](https://forum.search-guard.com/u/jkressin)\ **Post date:** [May 14, 2018, 9:28pm UTC](https://forum.search-guard.com/t/community-edition-limitations/905/4 "2018-05-14T21:28:32Z")
Which version of the Kibana plugin are you using? Is it the latest one? If you set this switch in elasticsearch.yml: searchguard.enterprise\_modules\_enabled: false `` all Enterprise features are disabled and there should not be any license warning at all, regardless of any expired trial license. Maby it is a bug in an older version of the Kibana plugin? > **···** > > On Monday, May 14, 2018 at 4:08:37 PM UTC+2, Matteo Cusmai wrote: > > > Hi Jochen, > > thanks for the quick reply. > > > > > > I have changed the date of my virtual machine in order to make expired the trial license, and when I open kibana I see the following message: > > > > > > ### Search Guard System Status > > > > [Back](http://ubuntu-16-elk:5601/app/searchguard-configuration#/) > > > The Search Guard license key is not valid for this cluster. Reason: > > > - License is expired > > > How I can delete the trial license since I, up to now, am not using the enterprise capabilities. > > > > > > Thanks a lot, > > > Matteo. > > > > > > > > > Matteo Cusmai > > > On Tue, May 8, 2018 at 6:51 PM, Jochen Kressin [jkressin@floragunn.com](mailto:jkressin@floragunn.com) wrote: > > > > > Hi, > > > > > > > > the code in the search-guard repository is the code for the Community Edition and Apache2 licensed: > > > > [https://github.com/floragunncom/search-guard](https://github.com/floragunncom/search-guard) > > > > [https://github.com/floragunncom/search-guard/blob/master/LICENSE](https://github.com/floragunncom/search-guard/blob/master/LICENSE) > > > > > > > > The code for the Enterprise and Compliance Edition is under a commercial license and can be found here: > > > > > > > > [https://github.com/floragunncom/search-guard-enterprise-modules](https://github.com/floragunncom/search-guard-enterprise-modules) > > > > [https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE](https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE) > > > > > > So as long as you are using the search-guard repo only, you are only using Apach2 licensed code and the Community Edition. > > > > > > > > We have also integrated a switch which will turn off all enterprise features, so you can be absolutely sure you only use the Community edition: > > > > > > > > [https://docs.search-guard.com/latest/search-guard-community-edition](https://docs.search-guard.com/latest/search-guard-community-edition) > > > > > > > > The Kibana Plugin is Apache2 licensed as well. > > > > > > > > So, judging from what you wrote, you are indeed using the Community Edition of Search Guard. > > > > On Tuesday, May 8, 2018 at 6:34:10 PM UTC+2, Matteo Cusmai wrote: > > > > > > > - Search Guard and Elasticsearch version 6.2.4 > > > > > - JVM version and operating system version 1.8 > > > > > > > > > > Hi all, > > > > > I am newbie on search guard, and I need to understand the limitation of community edition, so I have some questions: > > > > > - is the code on github under apache license? if so, is the code of community edition? > > > > - which is the best way to be sure that I am using the community edition? > > > > - I have compiled the plugins from github on my PC, and then I have installed the plugins on elastic and kibana, can I suppose that I am using the community edition of the plugins? > > > > Thanks a lot, > > > > > Matteo. > > > > – > > > > > > You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group. > > > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [search-guard+unsubscribe@googlegroups.com](mailto:search-guard+unsubscribe@googlegroups.com). > > > > > > To post to this group, send email to [search-guard@googlegroups.com](mailto:search-guard@googlegroups.com). > > > > > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/9f1ac54c-cdd7-4168-bc11-46aaf7da7c86%40googlegroups.com](https://groups.google.com/d/msgid/search-guard/9f1ac54c-cdd7-4168-bc11-46aaf7da7c86%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > ---
**Author:** ![praveensearchguard](https://avatars.discourse-cdn.com/v4/letter/p/8e7dd6/32.png) [@praveensearchguard](https://forum.search-guard.com/u/praveensearchguard)\ **Post date:** [March 15, 2019, 7:46am UTC](https://forum.search-guard.com/t/community-edition-limitations/905/5 "2019-03-15T07:46:46Z")
Hi Jochen, Greetings!! I also faced same issue as mentioned by matteo. As you suggested we have updated elasticsearch.yml. But with admin login also we are not get enabled with search guard console in kibana. we are simply getting login page for kibana after that we are not able to create any user since not getting search guard tab console in kibana UI. Kindly help us to get/ enable search guard in kibana UI Thanks, Praveen B > **···** > > On Tuesday, May 15, 2018 at 2:58:33 AM UTC+5:30, Jochen Kressin wrote: > > > Which version of the Kibana plugin are you using? Is it the latest one? If you set this switch in elasticsearch.yml: > > > searchguard.enterprise\_modules\_enabled: false > > > `` > > > all Enterprise features are disabled and there should not be any license warning at all, regardless of any expired trial license. Maby it is a bug in an older version of the Kibana plugin? > > > On Monday, May 14, 2018 at 4:08:37 PM UTC+2, Matteo Cusmai wrote: > > > > > Hi Jochen, > > > thanks for the quick reply. > > > > > > > > I have changed the date of my virtual machine in order to make expired the trial license, and when I open kibana I see the following message: > > > > > > > > ### Search Guard System Status > > > > > > [Back](http://ubuntu-16-elk:5601/app/searchguard-configuration#/) > > > > The Search Guard license key is not valid for this cluster. Reason: > > > > - License is expired > > > > How I can delete the trial license since I, up to now, am not using the enterprise capabilities. > > > > > > > > Thanks a lot, > > > > Matteo. > > > > > > > > > > > > Matteo Cusmai > > > > On Tue, May 8, 2018 at 6:51 PM, Jochen Kressin [jkre...@floragunn.com](mailto:jkre...@floragunn.com) wrote: > > > > > > > Hi, > > > > > > > > > > the code in the search-guard repository is the code for the Community Edition and Apache2 licensed: > > > > > [https://github.com/floragunncom/search-guard](https://github.com/floragunncom/search-guard) > > > > > [https://github.com/floragunncom/search-guard/blob/master/LICENSE](https://github.com/floragunncom/search-guard/blob/master/LICENSE) > > > > > > > > > > The code for the Enterprise and Compliance Edition is under a commercial license and can be found here: > > > > > > > > > > [https://github.com/floragunncom/search-guard-enterprise-modules](https://github.com/floragunncom/search-guard-enterprise-modules) > > > > > [https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE](https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE) > > > > > > > > So as long as you are using the search-guard repo only, you are only using Apach2 licensed code and the Community Edition. > > > > > > > > > > We have also integrated a switch which will turn off all enterprise features, so you can be absolutely sure you only use the Community edition: > > > > > > > > > > [https://docs.search-guard.com/latest/search-guard-community-edition](https://docs.search-guard.com/latest/search-guard-community-edition) > > > > > > > > > > The Kibana Plugin is Apache2 licensed as well. > > > > > > > > > > So, judging from what you wrote, you are indeed using the Community Edition of Search Guard. > > > > > On Tuesday, May 8, 2018 at 6:34:10 PM UTC+2, Matteo Cusmai wrote: > > > > > > > > > - Search Guard and Elasticsearch version 6.2.4 > > > > > > - JVM version and operating system version 1.8 > > > > > > > > > > > > Hi all, > > > > > > I am newbie on search guard, and I need to understand the limitation of community edition, so I have some questions: > > > > > > - is the code on github under apache license? if so, is the code of community edition? > > > > > - which is the best way to be sure that I am using the community edition? > > > > > - I have compiled the plugins from github on my PC, and then I have installed the plugins on elastic and kibana, can I suppose that I am using the community edition of the plugins? > > > > > Thanks a lot, > > > > > > Matteo. > > > > > – > > > > > > > > You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group. > > > > > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [search-guard...@googlegroups.com](mailto:search-guard...@googlegroups.com). > > > > > > > > To post to this group, send email to [search...@googlegroups.com](mailto:search...@googlegroups.com). > > > > > > > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/9f1ac54c-cdd7-4168-bc11-46aaf7da7c86%40googlegroups.com](https://groups.google.com/d/msgid/search-guard/9f1ac54c-cdd7-4168-bc11-46aaf7da7c86%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > ---
**Author:** ![praveensearchguard](https://avatars.discourse-cdn.com/v4/letter/p/8e7dd6/32.png) [@praveensearchguard](https://forum.search-guard.com/u/praveensearchguard)\ **Post date:** [March 15, 2019, 7:47am UTC](https://forum.search-guard.com/t/community-edition-limitations/905/6 "2019-03-15T07:47:27Z")
> Hi @Jochen, > Greetings!! > > I also faced same issue as mentioned by matteo. As you suggested we have updated elasticsearch.yml. But with admin login also we are not get enabled with search guard console in kibana. we are simply getting login page for kibana after that we are not able to create any user since not getting search guard tab console in kibana UI. Kindly help us to get/ enable search guard in kibana UI > > Thanks, > Praveen B > > > Which version of the Kibana plugin are you using? Is it the latest one? If you set this switch in elasticsearch.yml: > > searchguard.enterprise\_modules\_enabled: false > > `` > > all Enterprise features are disabled and there should not be any license warning at all, regardless of any expired trial license. Maby it is a bug in an older version of the Kibana plugin? > > > Hi Jochen, > > > thanks for the quick reply. > > > > > > I have changed the date of my virtual machine in order to make expired the trial license, and when I open kibana I see the following message: > > > > > > ### Search Guard System Status > > > > > > [Back](http://ubuntu-16-elk:5601/app/searchguard-configuration#/) > > > The Search Guard license key is not valid for this cluster. Reason: > > > - License is expired > > > How I can delete the trial license since I, up to now, am not using the enterprise capabilities. > > > > > > Thanks a lot, > > > Matteo. > > > > > > > > > Matteo Cusmai > > > > Hi, > > > > > > > > the code in the search-guard repository is the code for the Community Edition and Apache2 licensed: > > > > [https://github.com/floragunncom/search-guard](https://github.com/floragunncom/search-guard) > > > > [https://github.com/floragunncom/search-guard/blob/master/LICENSE](https://github.com/floragunncom/search-guard/blob/master/LICENSE) > > > > > > > > The code for the Enterprise and Compliance Edition is under a commercial license and can be found here: > > > > > > > > [https://github.com/floragunncom/search-guard-enterprise-modules](https://github.com/floragunncom/search-guard-enterprise-modules) > > > > [https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE](https://github.com/floragunncom/search-guard-enterprise-modules/blob/master/LICENSE) > > > > > > > > So as long as you are using the search-guard repo only, you are only using Apach2 licensed code and the Community Edition. > > > > > > > > We have also integrated a switch which will turn off all enterprise features, so you can be absolutely sure you only use the Community edition: > > > > > > > > [https://docs.search-guard.com/latest/search-guard-community-edition](https://docs.search-guard.com/latest/search-guard-community-edition) > > > > > > > > The Kibana Plugin is Apache2 licensed as well. > > > > > > > > So, judging from what you wrote, you are indeed using the Community Edition of Search Guard. > > > > > - Search Guard and Elasticsearch version 6.2.4 > > > > > - JVM version and operating system version 1.8 > > > > > > > > > > Hi all, > > > > > I am newbie on search guard, and I need to understand the limitation of community edition, so I have some questions: > > > > > - is the code on github under apache license? if so, is the code of community edition? > > > > > - which is the best way to be sure that I am using the community edition? > > > > > - I have compiled the plugins from github on my PC, and then I have installed the plugins on elastic and kibana, can I suppose that I am using the community edition of the plugins? > > > > > Thanks a lot, > > > > > Matteo. > > > > – > > > > > > > > You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group. > > > > > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [search-guard...@googlegroups.com](mailto:search-guard...@googlegroups.com). > > > > > > > > To post to this group, send email to [search...@googlegroups.com](mailto:search...@googlegroups.com). > > > > > > > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/9f1ac54c-cdd7-4168-bc11-46aaf7da7c86%40googlegroups.com](https://groups.google.com/d/msgid/search-guard/9f1ac54c-cdd7-4168-bc11-46aaf7da7c86%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > **···** > > On Friday, March 15, 2019 at 1:16:46 PM UTC+5:30, B Praveen wrote: > > > On Tuesday, May 15, 2018 at 2:58:33 AM UTC+5:30, Jochen Kressin wrote: > > > > > On Monday, May 14, 2018 at 4:08:37 PM UTC+2, Matteo Cusmai wrote: > > > > > > > On Tue, May 8, 2018 at 6:51 PM, Jochen Kressin [jkre...@floragunn.com](mailto:jkre...@floragunn.com) wrote: > > > > > > > > > On Tuesday, May 8, 2018 at 6:34:10 PM UTC+2, Matteo Cusmai wrote: