Docker - Mimoto - Unsatisfied dependency - cbeffutil

I am trying to run ‘docker-compose’ in ‘docker-compose-injistack’

I am stuck with an error starting ‘Mimoto Service’, bellow some error excerpts:

2025-03-06T18:06:45.302Z  WARN 1 --- [mimoto] [           main] [                                                 ] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'credentialShareServiceImpl': Unsatisfied dependency expressed through field 'util': Error creating bean with name 'cbeffToBiometricUtil': Unsatisfied dependency expressed through field 'cbeffutil': Error creating bean with name 'getCbeffUtil': Invocation of init method failed
2025-03-06T18:06:45.404Z ERROR 1 --- [mimoto] [           main] [                                                 ] o.s.boot.SpringApplication               : Application run failed
... 

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'credentialShareServiceImpl': Unsatisfied dependency expressed through field 'util': Error creating bean with name 'cbeffToBiometricUtil': Unsatisfied dependency expressed through field 'cbeffutil': Error creating bean with name 'getCbeffUtil': Invocation of init method failed
... 

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'cbeffToBiometricUtil': Unsatisfied dependency expressed through field 'cbeffutil': Error creating bean with name 'getCbeffUtil': Invocation of init method failed
... 
        ... 25 common frames omitted
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getCbeffUtil': Invocation of init method failed

Hi @Marcilio,

Thank you for reaching out. We are looking into this issue and one of our experts will get back to you shortly.

Best Regards
Team MOSIP

Hi @Marcilio
It can be some intermittent issue with internet. To resolve CbeffUtil, this url need to be resolved inji-certify/docker-compose/docker-compose-injistack/config/mimoto-default.properties at master · mosip/inji-certify · GitHub
If we see this, the url becomes https://raw.githubusercontent.com/mosip/mosip-config/develop/mosip-cbeff.xsd, and it’s accessible.

Are you still facing the issue?

Hi @swatigoel

I discovered that the problem is related to our corporate environment. It works at home, but it doesn’t work at the company.

At the company, we have a corporate outbound proxy to the internet.

When we use Docker, we configure it to use a local proxy that points to the corporate proxy. The HTTP_PROXY and HTTPS_PROXY properties set in the Docker configuration are injected into the container and are available to the OS.

The Mimoto project is using the obsolete java.net library to search for ‘cbeffutil’, but this library does not use the OS proxy variables to access the URI, and this is the reason for the access error that is occurring when I try to use this project in the corporate environment.

Thanks for the update @Marcilio
Do you need any other support now?

In fact, the one that uses java.net is the Cbeffimpl class, which comes from the mimoto dependency ‘io.mosip.kernel/kernel-cbeffutil-api/1.3.0-beta.1’

I will serve the necessary file locally (local network) and thus avoid the proxy problem. Thanks!

Sure @Marcilio,
We will also try to replicate this scenario at our end and let you know.