Hello,
we have a plugin that triggers search scroll requests in the cluster using an internal node client; these requests are rejected using version -17 and -18 on 5.6.x clusters as the scroll requests checks if a user is declared in the current thread context, but does not find any.
It seems that this issue was fixed in https://github.com/floragunncom/search-guard/commit/621db032fff5da3e12a0c8bdc35a7ef4c48e5ae7, will the fix be backported to the 5.6.x series?
Thanks,
Fabio Corneti
Hi Fabio,
yes, the fix will be backported to 5.6.x and released with the next version of SG.
On Tuesday, January 23, 2018 at 12:42:29 AM UTC+1, Fabio Corneti wrote:
Hello,
we have a plugin that triggers search scroll requests in the cluster using an internal node client; these requests are rejected using version -17 and -18 on 5.6.x clusters as the scroll requests checks if a user is declared in the current thread context, but does not find any.
It seems that this issue was fixed in https://github.com/floragunncom/search-guard/commit/621db032fff5da3e12a0c8bdc35a7ef4c48e5ae7, will the fix be backported to the 5.6.x series?
Thanks,
Fabio Corneti
Should be fixed here (for 5.6.6):
https://oss.sonatype.org/content/repositories/snapshots/com/floragunn/search-guard-5/5.6.6-19-SNAPSHOT/search-guard-5-5.6.6-19-20180126.110830-2.zip
Can you try if it works for you?
Am 25.01.2018 um 15:13 schrieb Jochen Kressin <jkressin@floragunn.com>:
Hi Fabio,
yes, the fix will be backported to 5.6.x and released with the next version of SG.
On Tuesday, January 23, 2018 at 12:42:29 AM UTC+1, Fabio Corneti wrote:
Hello,
we have a plugin that triggers search scroll requests in the cluster using an internal node client; these requests are rejected using version -17 and -18 on 5.6.x clusters as the scroll requests checks if a user is declared in the current thread context, but does not find any.It seems that this issue was fixed in https://github.com/floragunncom/search-guard/commit/621db032fff5da3e12a0c8bdc35a7ef4c48e5ae7, will the fix be backported to the 5.6.x series?
Thanks,
Fabio Corneti--
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.
To post to this group, send email to search-guard@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/7cc71421-639d-4341-83d5-a6f0108500ac%40googlegroups.com\.
For more options, visit https://groups.google.com/d/optout\.
Hello,
sorry for the late reply, that build is working fine.
Cheers,
Fabio
On Friday, January 26, 2018 at 11:09:38 AM UTC, Search Guard wrote:
Should be fixed here (for 5.6.6):
Can you try if it works for you?
great, we will include this in the next release
On Thursday, 1 February 2018 20:06:58 UTC+1, Fabio Corneti wrote:
Hello,
sorry for the late reply, that build is working fine.
Cheers,
Fabio
On Friday, January 26, 2018 at 11:09:38 AM UTC, Search Guard wrote:
Should be fixed here (for 5.6.6):
Can you try if it works for you?
Fixed in SG 5.6.7.
On Thursday, February 1, 2018 at 9:12:05 PM UTC+1, Search Guard wrote:
great, we will include this in the next release
On Thursday, 1 February 2018 20:06:58 UTC+1, Fabio Corneti wrote:
Hello,
sorry for the late reply, that build is working fine.
Cheers,
Fabio
On Friday, January 26, 2018 at 11:09:38 AM UTC, Search Guard wrote:
Should be fixed here (for 5.6.6):
Can you try if it works for you?