SUMMARY I’ve deployed AAI Jakarta version with aaf and tls disabled. All the pods are up and running and AAI REST APIs are working fine. However, SDC distribution is failing on AAI side because aai-modelloader is not able to make a connection with aai-babel when tls is disabled.   Below is the error:     2022-09-15 17:24:55.935 ERROR 7 --- [pool-2-thread-3] o.o.a.m.n.ArtifactDownloadManager        : MDLSVC2005E|MDLSVC2005E Failed to send POST request to http: //aai-babel.rockhoppers-jakarta:9516: Error posting artifact service-VepcSvc-csar.csar 15.0 to Babel: No Babel trust store defined|   org.onap.aai.modelloader.restclient.BabelServiceClientException: No Babel trust store defined        at org.onap.aai.modelloader.restclient.HttpsBabelServiceClient.getTrustManagers(HttpsBabelServiceClient.java:144)        at org.onap.aai.modelloader.restclient.HttpsBabelServiceClient.<init>(HttpsBabelServiceClient.java:113)        at org.onap.aai.modelloader.service.HttpsBabelServiceClientFactory.create(HttpsBabelServiceClientFactory.java:49)        at org.onap.aai.modelloader.notification.ArtifactDownloadManager.createBabelServiceClient(ArtifactDownloadManager.java:227)        at org.onap.aai.modelloader.notification.ArtifactDownloadManager.invokeBabelService(ArtifactDownloadManager.java:175)        at org.onap.aai.modelloader.notification.ArtifactDownloadManager.processToscaArtifacts(ArtifactDownloadManager.java:156)        at org.onap.aai.modelloader.notification.ArtifactDownloadManager.processDownloadedArtifacts(ArtifactDownloadManager.java:141)        at org.onap.aai.modelloader.notification.ArtifactDownloadManager.downloadArtifacts(ArtifactDownloadManager.java:97)        at org.onap.aai.modelloader.notification.EventCallback.activateCallback(EventCallback.java:68)        at org.onap.sdc.impl.NotificationConsumer.run(NotificationConsumer.java:71)        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)        at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)        at java.base/java.lang. Thread .run(Unknown Source)   As per the error above,  aai-babel is expecting the password even when tls is disabled. It was working fine in Frankfurt because the certs were hard-coded which is not the case with Jakarta as it has been changed here . However, aai-model-loader doesn’t seem to be supporting this change. OOM VERSION Jakarta  CONFIGURATION Values.global.tlsEnabled: false ues.globa.aafEnabled: false STEPS TO REPRODUCE Deploy SDC, AAI and message-router with aafEnabled set to false.  Distribute a service from SDC UI.  SDC distribution fails as aai-modelloader is not able to initialize SDC distribution client and aai-babel client.  EXPECTED RESULTS Distribution should pass without any connection issues with tls disabled ACTUAL RESULTS Distribution fails on AAI side with below error: 2022-09-15 17:24:55.935 ERROR 7 --- [pool-2-thread-3] o.o.a.m.n.ArtifactDownloadManager        : MDLSVC2005E|MDLSVC2005E Failed to send POST request to http: //aai-babel.rockhoppers-jakarta:9516: Error posting artifact service-VepcSvc-csar.csar 15.0 to Babel: No Babel trust store defined|