Unable find saved objects Error: Bad Request

Hello !
After making the upgrade from version 7.12 to 7.17 of elasticsearch, I encountered an issue in Kibana.
When using the search bar in the saved objects (stack management), a popup messages says “Unable find saved objects Error: Bad Request”,
and I’ve tested on the old cluster with 7.12 version and it works. Also I’ve try with full admin permission and it’s ok.
Can you tell me please, if it is possible to be an issue related to the last version of ror or can be a bug of kibana ?
The version of Elasticsearch is 7.17.2 with ReadonlyREST: 1.43.0_es7.17.2 enterprise.
Thank you !

Hello,

Sorry for the delay. I’m trying to reproduce this issue now. Could you provide your kibana, es logs and kibana.yml, and readonlyrest.yml config files. It will help with debugging the problem. Thank you.

Hello !
Kibana - Stack Management / Saved objects = search bar(when I want to search a popup messages says “Unable find saved objects Error: Bad Request”) but only as normal user.
I didn’t find anything in the logs.
This is the configuration of ROR:

readonlyrest:
  prompt_for_basic_auth: false
  access_control_rules:
  - name: "Full Admin Kibana"
    groups: ["full-admin"]
    indices: ["*"]
    kibana_access: "admin"
  - name: "Full Admin Users"
    groups: ["full-admin"]
    indices: ["*"]
    actions: ["*"]
  - name: "Client Admin Group Kibana"
    groups: ["client_admin"]
    indices: [".kibana_client_admin", "*"]
    kibana_access: "rw"
    kibana_index: ".kibana_client_admin"
  - name: "Client Admin Group 0"
    groups: ["client_admin"]
    indices: ["*"]
    actions: ["*"]
  - name: "filtru Kibana"
    groups: ["filtru"]
    indices: ["*"]
    filter: "{\n  \"bool\": {\n   \"must\": [\n       {\"term\":{\"df_country.keyword\": \"Ivory Coast\"}}\n       ]\n }\n }"
    kibana_access: "rw"
    kibana_index: ".kibana_filtru"
  - name: "filtru Kibana 1"
    groups: ["filtru"]
    indices: [".kibana_filtru" ,"*"]
    kibana_access: "rw"
    kibana_index: ".kibana_filtru"
  proxy_auth_configs:
  - name: "px1"
    user_id_header: "x-forwarded-user"
  users:
  - username: "fulladmin"
    groups: ["full-admin"]
    auth_key_sha256: "*****"
  - username: "user"
    groups: ["client_admin", "filtru"]
    proxy_auth:
      proxy_auth_config: "px1"
      users: ["user"]
  - username: "kibana"
    groups: ["full-admin"]
    auth_key_sha256: "*****"
  - username: "user2"
    groups: ["full-admin"]
    auth_key_sha256: "*****"
  jwt:
  - name: "jwt_provider"
    signature_algo: "RSA"
    signature_key: "*****"
    user_claim: "sub"
    header_name: "Authorization"

This is the configuration of kibana:

kibana.index: ".kibana"
elasticsearch.username: "fulladmin"
elasticsearch.password: ""
elasticsearch.requestTimeout: 360000
server.ssl.certificate: ""
server.ssl.key: ""
server.ssl.enabled: true
logging.dest: ""
logging:
  appenders:
    file:
      type: file
      fileName: 
      layout:
        type: pattern
        highlight: true
    rolling-file:
      type: rolling-file
      fileName: 
      policy:
        type: size-limit
        size: 100mb
      strategy:
        type: numeric
        pattern: '-%i'
        max: 10
      layout:
        type: pattern
  root:
      appenders: [default, rolling-file, file]
      level: info

pid.file: ""
path.data: ""
xpack.graph.enabled: false
xpack.ml.enabled: true
xpack.security.enabled: false
xpack.watcher.enabled: false
readonlyrest_kbn.proxy_auth_passthrough: true
readonlyrest_kbn.sessions_probe_interval_seconds: 3600
telemetry.enabled: false
monitoring.enabled: true
server.publicBaseUrl: 
xpack.encryptedSavedObjects.encryptionKey:

Thank you !

Hi, I tried to reproduce this issue but without a success. Is it possible to upgrade kibana/es plugins to the newest, 1.47.0 version? Because as I see you use version 1.43.0, but in the meantime, we fixed a few issues related to the stack management items visibility based on kibana access, so maybe it was also fixed.

Ok, thank you, I will try.