hyperledger
whitelisted DID found on prism-node logs
Is this a regression?
No
Description
Running docker logs of prism-node like docker logs local-prism-node-1 | grep "whitelist" (replace local with the container name) shows the following output:
*** shutting down gRPC server since JVM is shutting down
*** server shut down
OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
{"@timestamp":"2024-07-03T10:38:17.212Z","loggerName":"io.iohk.atala.prism.node.NodeApp","threadName":"main","level":"INFO","message":"Loading DID whitelist"}
{"@timestamp":"2024-07-03T10:38:17.349Z","loggerName":"io.iohk.atala.prism.node.NodeApp","threadName":"main","level":"INFO","message":"DID whitelist:\n- did:prism:106c458b95e57e16cbbd4b9566a52446c39949fdbd8cd8f876230ff243cf7b5a:Cj8KPRI7CgdtYXN0ZXIwEAFKLgoJc2VjcDI1NmsxEiEDVw1B_oShVvJ11AlVhLYv7OBO9sY9AOz8D5FoWoqI14c"}
I have confirmed this on all my cloud agents, this comes from the prism-node component, every time the agent boots up it shows that legend, regardless of mode (local or preprod).
It's always the same DID did:prism:106c458b95e57e16cbbd4b9566a52446c39949fdbd8cd8f876230ff243cf7b5a:Cj8KPRI7CgdtYXN0ZXIwEAFKLgoJc2VjcDI1NmsxEiEDVw1B_oShVvJ11AlVhLYv7OBO9sY9AOz8D5FoWoqI14c
Anyone else can confirm this on your cloud agents?
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in
local and preprod
Anything else?
No response
What is the version of the prism-node component?
This is a question about the prism-node component. Which the repository is still not public / Open Source. So you might not be able to follow the link.
I believe this was a feature about who can use NodeExplorer on the old PRISM node?
It was removed in the PR refactor!: Open source node #850 -> https://github.com/input-output-hk/atala-prism/pull/850/files#diff-e6552d6c815bc7e5db7b1997cde47de9d316156c47abeaa12bcd8d0b4e576bfcL177
@robertocarvajal do you have any further question or can we close this ticket?
PRISM Node version 2.2.1, which is the version recommended to use on the latest stable version of Identus v2.12
Since this is the recommended version of the official Identus release I guess most people will be using that version, I don't even know where I can look for newer versions or follow the development of prism-node unfortunately and you are right, I can't follow that link and confirm if it's the same issue that I see.
This part is removed from the prism-node 2.5, so the issue is not relevant anymore. CC: @robertocarvajal
