New release: Search Guard 53

Now available: Search Guard 53.

Search Guard 53 brings support for ES 7.17.0, additional functionality for JWT authentication, and bug fixes for OIDC login and Signals.

JWT: The JWT authenticator now allows you to specify expected values for audience and/or issuer claims. If one of these values is specified, a JWT will be only accepted if the value matches.

OIDC Login: The new OIDC redirect handling implemented in Search Guard 51.0 caused issues with many Identity Providers, as it required the specification of a wildcard for the OIDC redirect URI. This is not supported by the OIDC standard. This release reverts these changes; thus, login with the affected Identity Providers will work again. This fix also fixes issues with Kibana instances running on a non-empty base URL.

Signals: Using static inputs with certain values could cause issues with index mapping. Additionally, two issues with the Signals Kibana GUI were fixed.

You can find the full changelogs here:

You can find all versions here:

Search Guard Version Matrix

As always, we appreciate your feedback, questions, and feature requests here on the forum.

Many greetings from the Search Guard team

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

Coded with love in Berlin, Denmark, Sweden, Italy, Ukraine 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.

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