Hi ,
after upgrading both the cluster and to 1.18.4_es6.8.2 and to Kibana enterprise to
readonlyrest_kbn_enterprise-1.18.4_es6.8.2.zip
The kibana works fine for users in the standard basic auth,
but SAML seems to have broken,
It was just redirecting to logout and I checked to see if there was some issue with the signature_key, as the docs say it needs to be 256min char, and i’m not sure if that’s a new or newly enforced requirement but i bellieve my working string was not full 256char before. so I generated a new 256char length string and after adjusting readonlyrest.yml and kibana.yml, upon clicking saml login, i get this 400 error directly
Any ideas? @sscarduzio
{“statusCode”:400,“error”:“Bad Request”,“message”:“Invalid cookie value”}
Yes this is fixed in master, we’re fixing some bugs with reporting and then release!
Thanks, will this also be fixed then in 7.2 also in a release for that ES version? I’m planning to continue to upgrade through to the latest ES version with ror and ror ent kbn support
Yes, in all versions >= 6.6.0
Thanks, is there any estimated date for this fix?