ID Authentication Deployment Problem (MOSIP v1.2.0.1-B1)

We are facing an error in the deploy of ID Authentication, in kubernetes.

Could not resolve placeholder ‘’ in value "${}"\n\tat org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(\n\tat\n\tat\n\tat\n\tat$doGetBean$0(\n\tat\n\tat\n\tat\n\tat org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(\n\tat\n\tat\n\tat org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.

Thank you,

@slimab please check whether softhsm-ida is installed or not and make sure to pass the same secrets to config-server.

the softhsm-ida was installed before the deployment ID authentification and the softhsm kernel services is correctly used by the keymanager

With reference to the latest inputs provided, in order to further investigate the issue, kindly verify the operational status of the config-server. Additionally, please ensure the existence of the environmental variable SPRING_CLOUD_CONFIG_SERVER_OVERRIDES_SOFTHSM_IDA_PIN within the deployment of the config-server in the namespace of the config-server.


Now we are facing anthore error, in two pods (auth and otp) of deploy of ID Authentication.


IDR-IDC-004 → Unknown error occurred; \nnested exception is io.mosip.kernel.auth.defaultadapter.exception.AuthAdapterException: Self cached auth token is null\n\t… 61 common frames omitted\nCaused by: io.mosip.kernel.auth.defaultadapter.exception.AuthAdapterException: Self cached auth token is null\n\tat io.mosip.kernel.auth.defaultadapter.config.SelfTokenExchangeFilterFunction.filter(\n\tat org.springframework.web.reactive.function.client.ExchangeFilterFunction.lambda$andThen$1(\n\tat org.springframework.web.reactive.function.client.ExchangeFilterFunction.lambda$apply$2(\n\tat org.springframework.web.reactive.function.client.DefaultWebClient$\n\tat org.springframework.web.reactive.function.client.DefaultWebClient$DefaultRequestBodyUriSpec.retrieve(\n\tat io.mosip.idrepository.core.helper.RestHelper.request(\n\tat io.mosip.idrepository.core.helper.RestHelper.requestSync(\n\t… 60 common frames omitted\n",“appName”:“id-authentication,id-authentication-external”}

{“@timestamp”:“2023-04-19T12:08:57.045Z”,“@version”:“1”,“message”:“Error connecting to OIDC service (WebClient) Problem in connecting to auth service or UNKNOWN Error.”,“logger_name”:“io.mosip.kernel.auth.defaultadapter.helper.TokenHelper”,“thread_name”:“main”,“level”:“ERROR”,“level_value”:40000,“appName”:“id-authentication,id-authentication-external”}
{“@timestamp”:“2023-04-19T12:08:57.045Z”,“@version”:“1”,“message”:“there is some issue with getting token with clienid and secret”,“logger_name”:“io.mosip.kernel.auth.defaultadapter.config.SelfTokenExchangeFilterFunction”,“thread_name”:“main”,“level”:“ERROR”,“level_value”:40000,“appName”:“id-authentication,id-authentication-external”}

Hello @slimab ,

To obtain the complete logs of the IDA authentication and IDA OTP service, you can use the following command:

kubectl -n <namespace> logs <pod-name> --previous

Please replace <namespace> and <pod-name> with the appropriate values for your setup.

Based on the exception you provided, it seems that there is an issue with connecting to the OIDC authentication service. To investigate this further, I will need the configuration properties files for the OIDC, kernel, and IDA modules. Additionally, please provide information on which version of OIDC you have deployed.

Please provide the requested information so that I can assist you further.


Hello @syed.salman,
What do you mean exactly by the configuration properties files for the OIDC, kernel, and IDA modules?
If you need configmaps and secret, from which namespace do you need them?
if you need files properties from config-server module, what files do you need them?


@slimab we face OIDC related issues as mentioned in IDA logs

  1. due to connection issue to keycloak
  2. due to wrong client ID / secret for the mpartner-default-auth in IDA config. Due to above reasons IDA might be not be able to create token and validate the same.


  1. check the keycloak connectivity issue and fix.
  2. In case keycloak init was done after config server deployment due to any reason, redeploy config server after deleting so that it gets correct secret and passes the same to IDA. Please do restart the IDA failing services once config server is redeployed.

Hello @ckm007,
replaying on your answer:
1- curling the link of keycloak: curl http://x.x.x.x:8080/auth/realms/mosip, from the istio of IDA AUTH, it provides the result:

The IDA AUTH pod is still down.