Publication #433 to target system HybrisCore failed

[karnwal_ankit]

We are getting the authentication failed exception in datahub. Currently using the default admin/nimda password for datahub and the application was in running status without any issue. Below is the error stack :

2020-09-18 00:04:17,551 [INFO ][defaultTaskExecutor-3][com.hybris.datahub.core.client.impl.DefaultExportClient] Status of the response from publish to target system: HybrisCore, 401 2020-09-18 00:04:17,552 [ERROR][defaultTaskExecutor-3][com.hybris.datahub.service.impl.PublicationActionHandler] Publication #433 to target system HybrisCore failed com.hybris.datahub.api.publication.PublicationException: An error occurred during the export of impex file at com.hybris.datahub.core.adapter.impl.DefaultCoreAdapterPublicationService.targetSystemPublication(DefaultCoreAdapterPublicationService.java:61) at com.hybris.datahub.core.adapter.impl.DefaultCoreAdapterPublicationService.publish(DefaultCoreAdapterPublicationService.java:39) at com.hybris.datahub.core.adapter.impl.CoreAdapterService.publish(CoreAdapterService.java:76) at com.hybris.datahub.service.publication.impl.DefaultDataHubPublicationService.startPublication(DefaultDataHubPublicationService.java:238) at com.hybris.datahub.service.publication.impl.DefaultDataHubPublicationService.publish(DefaultDataHubPublicationService.java:98) at jdk.internal.reflect.GeneratedMethodAccessor521.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:295) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:98) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212) at com.sun.proxy.$Proxy150.publish(Unknown Source) at com.hybris.datahub.service.impl.PublicationActionHandler.publishToTargetSystems(PublicationActionHandler.java:355) at com.hybris.datahub.service.impl.PublicationActionHandler.handlePublicationAction(PublicationActionHandler.java:133) at com.hybris.datahub.service.impl.PublicationActionHandler.handleAction(PublicationActionHandler.java:97) at com.hybris.datahub.service.impl.PublicationActionHandler.handleAction(PublicationActionHandler.java:71) at com.hybris.datahub.command.impl.AbstractPerformCommand.lambda$execute$0(AbstractPerformCommand.java:56) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736) at com.hybris.datahub.service.ExceptionHandlingAsyncTaskExecutor.lambda$createWrappedRunnable$1(ExceptionHandlingAsyncTaskExecutor.java:72) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.lang.SecurityException: Authentication failed for target system at com.hybris.datahub.core.client.impl.DefaultExportClient.validateExportResponse(DefaultExportClient.java:238) at com.hybris.datahub.core.client.impl.DefaultExportClient.export(DefaultExportClient.java:99) at com.hybris.datahub.core.adapter.impl.DefaultCoreAdapterPublicationService.targetSystemPublication(DefaultCoreAdapterPublicationService.java:56) ... 25 common frames omitted

[Slava]

Ankit, default password was removed from DataHub properties files a few patch cycles ago. The reasoning is exactly that - people use the default password, which makes an easy guess for a potential attacker. For that reason, the password must be configured explicitly and it's better to use a non-default value.