Esignet application error

Hi Team,

While setting up esignet, the pod is getting failed due to the below error

mestamp":“2024-03-22T08:57:56.416Z”,“@version”:“1”,“message”:"
\n\n***************************\nAPPLICATION FAILED TO START\n***************************
\n\nDescription:
\n\nField vcIssuancePlugin in io.mosip.esignet.vci.services.VCIssuanceServiceImpl required a bean of type ‘io.mosip.esignet.api.spi.VCIssuancePlugin’ that could not be found.
\n\nThe injection point has the following annotations:\n\t- @org.springframework.beans.factory.annotation.Autowired(required=true)\n\n\nAction:
\n\nConsider defining a bean of type ‘io.mosip.esignet.api.spi.VCIssuancePlugin’ in your configuration.
\n",“logger_name”:“org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter”,
“thread_name”:“main”,“level”:“ERROR”,“level_value”:40000,“appName”:“esignet”}

I tried updating the conf-server and no luck. Need help!

Hello @ali_shaik,

Based on the error posted, the eSignet service has failed to find the VCIssuancePlugin implementation in its classpath(runtime dependency).

Please check the mock implementation of the VCIssuancePlugin interface here.

Also, make sure the right configurations are updated in the esignet-default.properties based on the VCIIssuancePlugin implementation used. Check here for more information.

regards,
Anusha S E

1 Like

Hi,

For the VCIssuancePlugin implementation, I was trying to deploy the mock esignet services. The pod is failing due to the below error


{“@timestamp”:“2024-03-27T09:50:10.644Z”,“@version”:“1”,“message”:“Application run failed”,“logger_name”:“org.springframework.boot.SpringApplication”,“thread_name”:“main”,“level”:“ERROR”,“level_value”:40000,“stack_trace”:"java.lang.IllegalStateException: Failed to execute ApplicationRunner\n\tat org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:789)\n\tat org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:776)\n\tat org.springframework.boot.SpringApplication.run(SpringApplication.java:322)\n\tat org.springframework.boot.SpringApplication.run(SpringApplication.java:1237)\n\tat org.springframework.boot.SpringApplication.run(SpringApplication.java:1226)\n\tat io.mosip.esignet.mock.identitysystem.MockIdentitySystemApplication.main(MockIdentitySystemApplication.java:20)\n\tat java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.base/java.lang.reflect.Method.invoke(Method.java:566)\n\tat org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)\n\tat org.springframework.boot.loader.Launcher.launch(Launcher.java:107)\n\tat org.springframework.boot.loader.Launcher.launch(Launcher.java:58)\n\tat org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:467)\nCaused by: io.mosip.kernel.core.keymanager.exception.NoSuchSecurityProviderException: KER-KMA-004 → No such alias: c85f7828-4dc0-4101-9eb7-0e7587f1bb0c\n\tat io.mosip.kernel.keymanager.hsm.impl.pkcs.PKCS11KeyStoreImpl.getAsymmetricKey(PKCS11KeyStoreImpl.java:295)\n\tat io.mosip.kernel.keymanager.hsm.impl.pkcs.PKCS11KeyStoreImpl.getCertificate(PKCS11KeyStoreImpl.java:377)\n\tat io.mosip.kernel.keymanager.hsm.impl.pkcs.PKCS11KeyStoreImpl.getCertificate(PKCS11KeyStoreImpl.java:63)\n\tat io.mosip.k


Is there any specific configuration needed for the mock services? also, is there any step by step guide to follow for a deployment?

Hi @ali_shaik

esignet-mock-services/mock-identity-system will need SoftHSM to store the keys. The key references are stored in the DB in the key_alias table.

Based on the error shared, seems like Db has the key references which is not present in SoftHSM.

You could try truncating the key_alias table in the mock_identity_system DB and restart the mock-identity-system.

thanks & regards

Thanks for the resolution and it has resolved the issue. But, the pod is getting restarted repeatedly without any errors in the logs.

Need help