[BUG] Spring-boot-dependencies:3.3.9 incompatible with azure-sdk-bom:1.2.24-1.2.32

[Simon-Wang-Depot-Project]

Describe the bug
My Spring Boot application, currently running on version 3.3.5 with spring-boot-dependencies and azure-sdk-bom version 1.2.16, successfully authenticates to Azure services (Cosmos DB, Azure Storage, Service Bus, etc.) using DefaultAzureCredential configured via environment variables (AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID or Managed Identity). However, after upgrading Spring Boot to version 3.3.9, I'm experiencing an incompatibility issue with the azure-sdk-bom. Testing with versions 1.2.16, 1.2.24 and 1.2.32 results in an UnresolvedAddressException during the DefaultAzureCredential initialization process.

Exception or Stack Trace
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Suppressed: com.azure.core.exception.ClientAuthenticationException: DefaultAzureCredential authentication failed. ---> EnvironmentCredential authentication failed. Error Details: java.nio.channels.UnresolvedAddressException
at com.azure.identity.ChainedTokenCredential.lambda$handleExceptionAsync$5(ChainedTokenCredential.java:120)
at reactor.core.publisher.Mono.lambda$onErrorResume$30(Mono.java:3938)
at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onError(FluxOnErrorResume.java:94)
... 59 common frames omitted
Caused by: com.microsoft.aad.msal4j.MsalClientException: java.nio.channels.UnresolvedAddressException

Expected behavior
Based on the document, azure-sdk-bom 1.2.24 - 1.2.32 is compatible with spring-boot-dependencies:3.3.9. (https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use)

Any suggestions on how to resolve this incompatibility would be very helpful.

[junior-juarez-MSFT]

I'm from OSS and checked this issue with @Simon-Wang-Depot-Project using lower version of Spring Boot (3.3.5) the app code works as expected and connects to CosmosDB. Initially Simon tried to fix a CVE on tomcat-embded-core https://mvnrepository.com/artifact/org.apache.tomcat.embed/tomcat-embed-core/10.1.31 to overcome that had to upgrade Spring Boot to v3.3.9.

Out of curiosity, BOM SDK is using Msal4j where the UnresolvedAddressException seems to come from.

We nslookup and tested connectivity to comosDB from the local environment Simon is working on. DNS resolved and were able to get a response from Cosmos.

[alzimmermsft]

@billwert, @g2vinay, could you give this a first pass look as the primary stack trace is in the Identity package / its dependencies. I'm also adding the HttpClient tag as my intuition is telling me it's likely that this issue will end up being something with azure-core-http-netty / Reactor Netty behavioral changes with the dependency changes.

[billwert]

@junior-juarez-MSFT @Simon-Wang-Depot-Project Thanks for the report!

I don't think I see it here - what was the last working version of the BOM for you? Does any version of the BOM work with Spring Boot v3.3.9?

Also, can you share the full stack trace?

The exception coming from msal4j here isn't super useful. msal4j is wrapping an HttpClient we are passing to it and using it. In this instance the target would not be Cosmos but an identity endpoint (like login.microsoft.com.) This makes your intuition more likely, @alzimmermsft.