v3.0.1 introduced an incompatible change in the WebSecurityAutoConfiguration: @ConditionalOnMissingBean was applied to the SecurityFilterChain-Bean, leading to unexpected behaviour in downstream consumers. This release reinstates the previous behaviour.
If applications want to replace the WebSecurityAutoConfiguration completely, they can do so by deactivating WebSecurityAutoConfiguration via spring.autoconfigure.exclude and replacing it with a single instance of their own, if required.