frontend: impossible to authorize users in your application

[veonline]

in the fontend's Authorize users in your application modal, the left panel remains always empty when i use the filter.

i've checked the logs from keyrock and found a clue that seems to point to some query string sanitization error. logs below

keyrock version: 8.3.0

fiware-keyrock | 2022-11-04T09:13:20.965Z idm:web-authorize_user_app_controller --> available_users
fiware-keyrock | (node:19) UnhandledPromiseRejectionWarning: Error: Invalid value { like: '%en%' }
fiware-keyrock |     at Object.escape (/opt/fiware-idm/node_modules/sequelize/lib/sql-string.js:52:11)
fiware-keyrock |     at MySQLQueryGenerator.escape (/opt/fiware-idm/node_modules/sequelize/lib/dialects/abstract/query-generator.js:709:22)
fiware-keyrock |     at MySQLQueryGenerator._whereParseSingleValueObject (/opt/fiware-idm/node_modules/sequelize/lib/dialects/abstract/query-generator.js:1972:41)
fiware-keyrock |     at MySQLQueryGenerator.whereItemQuery (/opt/fiware-idm/node_modules/sequelize/lib/dialects/abstract/query-generator.js:1730:19)
fiware-keyrock |     at /opt/fiware-idm/node_modules/sequelize/lib/dialects/abstract/query-generator.js:1649:25
fiware-keyrock |     at Array.forEach (<anonymous>)
fiware-keyrock |     at MySQLQueryGenerator.whereItemsQuery (/opt/fiware-idm/node_modules/sequelize/lib/dialects/abstract/query-generator.js:1647:35)
fiware-keyrock |     at MySQLQueryGenerator.getWhereConditions (/opt/fiware-idm/node_modules/sequelize/lib/dialects/abstract/query-generator.js:1990:19)
fiware-keyrock |     at MySQLQueryGenerator.selectQuery (/opt/fiware-idm/node_modules/sequelize/lib/dialects/abstract/query-generator.js:932:28)
fiware-keyrock |     at MySQLQueryInterface.select (/opt/fiware-idm/node_modules/sequelize/lib/dialects/abstract/query-interface.js:407:59)
fiware-keyrock |     at Function.findAll (/opt/fiware-idm/node_modules/sequelize/lib/model.js:1134:47)
fiware-keyrock |     at processTicksAndRejections (internal/process/task_queues.js:95:5)

[danijelakrstic]

Is there any news about this issue in version 8.3.0? Does anyone know when the issue will be fixed?

[apozohue10]

Hello,

the bug has been fixed in master branch. We will release 8.3.1 with this fix included.

BR