-
Notifications
You must be signed in to change notification settings - Fork 85
Description
Hi,
I'm trying to set up a Keyrock instance at the moment using the newest release 8.4.0 on Ubuntu. When I try to start the server after following the installation steps in the documentation the web GUI is reachable and I can interact with it but the following error is thrown:
(node:1733) UnhandledPromiseRejectionWarning: Error: missing key for signatory 0
at /opt/fiware-idm/node_modules/node-jose/lib/jws/sign.js:294:26
at Array.map ()
at Object.createSign (/opt/fiware-idm/node_modules/node-jose/lib/jws/sign.js:272:23)
at Object.create_jwt (/opt/fiware-idm/controllers/extparticipant/utils.js:283:25)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async retrieve_participant_registry_token (/opt/fiware-idm/controllers/extparticipant/utils.js:111:10)
at async fetch_access_token (/opt/fiware-idm/controllers/extparticipant/utils.js:309:19)
at async inner_get_access_token (/opt/fiware-idm/controllers/extparticipant/utils.js:347:14)
at async fetch_trusted_list (/opt/fiware-idm/controllers/extparticipant/utils.js:359:26)
(node:1733) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:1733) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The following versions are installed:
Ubuntu: 22.04
Nodejs: v18.19.1
Npm: 10.2.4
Could you help me solve this error?
Edit to add:
The issue does not appear in Keyrock version 8.3.3.