[FEATURE REQ] Deprecate the implementations from WebSecurityConfigurerAdapter

[moarychan]

Context

Since the WebSecurityConfigurerAdapter has been deprecated, then the below class should be updated to provide a new configurer for HTTP security,

azure-sdk-for-java/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/aad/AadWebSecurityConfigurerAdapter.java

Line 38 in 2c884a4

public abstract class AadWebSecurityConfigurerAdapter extends WebSecurityConfigurerAdapter {

azure-sdk-for-java/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/aad/AadResourceServerWebSecurityConfigurerAdapter.java

Line 22 in 2c884a4

public abstract class AadResourceServerWebSecurityConfigurerAdapter extends WebSecurityConfigurerAdapter {

We should refer to the new configuer from feature/spring-boot-3 branch,

azure-sdk-for-java/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/aad/AadResourceServerHttpSecurityConfigurer.java

Line 24 in a77e4b3

public class AadResourceServerHttpSecurityConfigurer extends AbstractHttpConfigurer<AadResourceServerHttpSecurityConfigurer, HttpSecurity> {

azure-sdk-for-java/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/aad/AadWebApplicationHttpSecurityConfigurer.java

Line 37 in a77e4b3

public class AadWebApplicationHttpSecurityConfigurer extends AbstractHttpConfigurer<AadWebApplicationHttpSecurityConfigurer, HttpSecurity> {

Goal

• Marked the AadXXAdapter as deprecated APIs.
• Provide the new way based on AbstractHttpConfigurer for Azure AD autoconfigure.

[samhanes-fs]

While this is being worked on, would it be possible to add an @ConditionalOnMissingBean condition for org.springframework.security.web.SecurityFilterChain to the DefaultAadResourceServerWebSecurityConfigurerAdapter bean in AadResourceServerConfiguration so that projects using the starter can adopt Spring's recommendations?

Without that condition, attempting to use a SecurityFilterChain causes a bunch of Spring container wiring errors because many of the Spring Security beans are being created twice.