rahul-ghadge / spring-boot-mongodb-crud Goto Github PK

As title, the lastest version of mongo, not allow seperate setting under application properties and cause authentication errors.

ref.

If you use the Mongo 3.0 Java driver, spring.data.mongodb.host and spring.data.mongodb.port are not supported. In such cases, spring.data.mongodb.uri should be used to provide all of the configuration.

The following uri setting works.

spring.data.mongodb.uri=mongodb://admin:123456@localhost:27017/spring_boot_mongo_app?authSource=admin&readPreference=primary&appname=MongoDB%20Compass&ssl=false

Before starts the app, should run the following commands to create db admin with user name as admin and password as 123456.

docker exec -it mongo mongo admin

db.createUser({ user:'admin',pwd:'123456',roles:[ { role:'userAdminAnyDatabase', db: 'admin'},"readWriteAnyDatabase"]}

code

We currently have a CORS filter (CORSFilter) in our codebase to handle Cross-Origin Resource Sharing. However, there is a more modern and Spring-centric approach using WebMvcConfigurer. This issue aims to replace the existing CORSFilter with the WebMvcConfigurer-based configuration.

PROPOSED CHANGES
Replace the existing CORSFILTER.java class under config with the following configurtaion in DatabaseConfiguration.java

@Bean
public WebMvcConfigurer corsConfigurer() {
    return new WebMvcConfigurer() {
        @Override
        public void addCorsMappings(CorsRegistry registry) {
            registry.addMapping("/**")
                    .allowedOrigins("*")
                    .allowedMethods("*")
                    .allowedHeaders("*")
                    .allowCredentials(false).maxAge(3600);
        }
    };
}

This approach is more in line with modern Spring practices and provides a concise and effective way to handle CORS globally in our Spring Boot application and thereby reduces the boilerplate code