Search Guard 7.0.0 RC1 released

#1

Hi all,

I am very proud to announce the arrival of Search Guard 7 RC 1, compatible with Elasticsearch 7.0.0.

It is our release candidate and contains all breaking changes and new features.

Installing Search Guard on Elasticsearch:
bin/elasticsearch-plugin install https://repo1.maven.org/maven2/com/floragunn/search-guard-7/7.0.0-35.0.0-rc1/search-guard-7-7.0.0-35.0.0-rc1.zip

Installing Search Guard on Kibana:
bin/kibana-plugin install https://repo1.maven.org/maven2/com/floragunn/search-guard-kibana-plugin/7.0.0-35.0.0-rc1/search-guard-kibana-plugin-7.0.0-35.0.0-rc1.zip

Please give it a try and report any bugs and issues on GitHub:

Search Guard:

Kibana Plugin:

We have also updated our documentation and assembled a changelog and a upgrade guide.

The two most interesting changes in this release are:

New configuration syntax
The configuration syntax for Search Guard 6 suffered from some flaws and glitches which made it sometimes difficult to implement improvements and new feature requests. We have streamlined the configuration to remove these barriers. For example, the new format does now allow dots (.) in index names and regular expressions. We also introduced strict config syntax validation which rejects invalid syntax as well as configuration parameters which do not exist. The REST API and sgadmin will automatically apply these checks.

Built-in resources
In Search Guard 6, all roles and action groups are dynamically configured and stored in the Search Guard configuration index. This also includes common roles for Kibana, logstash and Beats and common action groups like sg_readall. In case the permissions for these roles changed when upgrading Elasticsearch, the roles needed to be updated manually as well. In Search Guard 7 all common roles will be static, so permission changes are automatically applied when upgrading Search Guard alongside Elasticsearch. The same applies to action groups.

The final release is expected to be released next week.

Known Issues
There is a known issue in this release with regards to Kibana multitenancy when upgrading from Elasticsearch 6. After upgrading the cluster the first attempt to start Kibana 7 may fail with an “index template missing exception” error message. In this case, the workaround is to stop Kibana and start it again. The second attempt to start Kibana 7 will then be successful.

Hendrik and the Search Guard team!


Search Guard (®) is an Elasticsearch plugin that offers encryption, authentication, and authorization.

Coded with love in Berlin, Denmark, Sweden, Italy and the US.

Search Guard is a trademark of floragunn GmbH, registered in the U.S. and in other countries.

Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries.

ETA for Elasticsearch 7.0.0 support?
#2

Hi,
When can we expect the official delivery of searchguard-7(Not the release candidates).

#3

Did you find any issues while testing beta1 and rc1?

#4

I have tested with release candidate ones and created some users, roles and rolesmapping. I am not facing any issues.

#5

SG7 GA is here:

closed #6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.