Database User Management Integration
Integrate Spring Security with a database to manage and authenticate users stored in a persistent data source.
Database User Management Integration is a free Spring Security 6 & JWT Authentication lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Spring Security 6 & JWT Authentication learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
DB for User Management
Welcome! So far, we've used in-memory users. But real applications need to store user data persistently. That's where databases come in!
In this lesson, you'll learn how to integrate Spring Security with a database to manage and authenticate your application's users.
Why Use a Database?
Storing users in a database offers several key benefits:
- Persistence: User data isn't lost when your app restarts.
- Scalability: Easily manage a large number of users.
- Flexibility: Store additional user attributes (e.g., email, roles, profile info).
- Centralized Management: A single source of truth for all user data.
Basic User Table
First, we need a database table to hold our users. A simple users table and an authorities table (for roles) might look like this:
These tables typically contain at least a username, password, and an 'enabled' status for the user, and a username and authority (role) for permissions.
CREATE TABLE users (
username VARCHAR(50) NOT NULL PRIMARY KEY,
password VARCHAR(500) NOT NULL,
enabled BOOLEAN NOT NULL
);
CREATE TABLE authorities (
username VARCHAR(50) NOT NULL,
authority VARCHAR(50) NOT NULL,
CONSTRAINT fk_authorities_users FOREIGN KEY (username) REFERENCES users (username)
);Custom UserDetailsService
Recall that UserDetailsService is the core interface Spring Security uses to retrieve user details. For database integration, we'll create or use an implementation that fetches user data from our database.
This service builds a UserDetails object (containing username, password, and roles) from the retrieved data.
package org.springframework.security.core.userdetails;
public interface UserDetailsService {
UserDetails loadUserByUsername(String username)
throws UsernameNotFoundException;
}Using JdbcUserDetailsManager
Spring Security provides JdbcUserDetailsManager, a convenient built-in implementation of UserDetailsService that uses JDBC (Java Database Connectivity) to interact with your database.
It expects specific table schemas (like the one shown earlier) to function correctly. You just need to provide it with a DataSource.
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.provisioning.JdbcUserDetailsManager;
import javax.sql.DataSource;
@Configuration
public class UserManagementConfig {
@Bean
public UserDetailsService userDetailsService(DataSource dataSource) {
JdbcUserDetailsManager userDetailsManager = new JdbcUserDetailsManager(dataSource);
// Custom queries can be set if your schema differs:
// userDetailsManager.setUsersByUsernameQuery("SELECT ...");
// userDetailsManager.setAuthoritiesByUsernameQuery("SELECT ...");
return userDetailsManager;
}
}Secure Password Storage
When storing passwords in a database, it's crucial to never store them in plain text. Always use a Password Encoder to hash them securely.
BCryptPasswordEncoder is a popular and robust choice, providing strong, one-way hashing for passwords.
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder;
import org.springframework.security.crypto.password.PasswordEncoder;
@Configuration
public class PasswordEncoderConfig {
@Bean
public PasswordEncoder passwordEncoder() {
return new BCryptPasswordEncoder();
}
}Wiring Authentication
To complete the integration, we need to tell Spring Security to use our database-backed UserDetailsService and the chosen PasswordEncoder.
This is typically done by configuring the SecurityFilterChain, where we explicitly set these components for authentication.
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.crypto.password.PasswordEncoder;
import org.springframework.security.web.SecurityFilterChain;
@Configuration
@EnableWebSecurity
public class WebSecurityConfig {
private final UserDetailsService userDetailsService;
private final PasswordEncoder passwordEncoder;
public WebSecurityConfig(UserDetailsService userDetailsService, PasswordEncoder passwordEncoder) {
this.userDetailsService = userDetailsService;
this.passwordEncoder = passwordEncoder;
}
@Bean
public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
http
.authorizeHttpRequests(authorize -> authorize
.anyRequest().authenticated()
)
.formLogin(form -> form.permitAll())
.userDetailsService(userDetailsService)
.passwordEncoder(passwordEncoder);
return http.build();
}
}Complete DB Auth Example
Here's a full runnable Spring Boot application that uses an in-memory H2 database, JdbcUserDetailsManager, and BCryptPasswordEncoder. It also creates some initial users.
Run it, then try to access /hello. You'll be prompted to log in with 'user'/'password' or 'admin'/'adminpass'.
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.jdbc.datasource.embedded.EmbeddedDatabaseBuilder;
import org.springframework.jdbc.datasource.embedded.EmbeddedDatabaseType;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.core.userdetails.User;
import org.springframework.security.core.userdetails.UserDetails;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder;
import org.springframework.security.crypto.password.PasswordEncoder;
import org.springframework.security.provisioning.JdbcUserDetailsManager;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
import javax.sql.DataSource;
@SpringBootApplication
@RestController
public class DatabaseAuthApp {
public static void main(String[] args) {
SpringApplication.run(DatabaseAuthApp.class, args);
}
@GetMapping("/hello")
public String hello() {
return "Hello, secured world!";
}
@Configuration
@EnableWebSecurity
static class WebSecurityConfig {
// 1. Configure DataSource for H2 in-memory database
@Bean
public DataSource dataSource() {
return new EmbeddedDatabaseBuilder()
.setType(EmbeddedDatabaseType.H2)
.addScript("classpath:org/springframework/security/core/userdetails/jdbc/users.ddl")
.build();
}
// 2. Configure JdbcUserDetailsManager to use the DataSource
@Bean
public UserDetailsService userDetailsService(DataSource dataSource, PasswordEncoder passwordEncoder) {
JdbcUserDetailsManager userDetailsManager = new JdbcUserDetailsManager(dataSource);
// Create initial users if they don't exist
if (!userDetailsManager.userExists("user")) {
UserDetails user = User.builder()
.username("user")
.password(passwordEncoder.encode("password"))
.roles("USER")
.build();
userDetailsManager.createUser(user);
}
if (!userDetailsManager.userExists("admin")) {
UserDetails admin = User.builder()
.username("admin")
.password(passwordEncoder.encode("adminpass"))
.roles("ADMIN", "USER")
.build();
userDetailsManager.createUser(admin);
}
return userDetailsManager;
}
// 3. Configure PasswordEncoder
@Bean
public PasswordEncoder passwordEncoder() {
return new BCryptPasswordEncoder();
}
// 4. Configure SecurityFilterChain
@Bean
public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
http
.authorizeHttpRequests(authorize -> authorize
.requestMatchers("/admin/**").hasRole("ADMIN") // Example role-based access
.anyRequest().authenticated()
)
.formLogin(form -> form
.permitAll()
)
.logout(logout -> logout
.permitAll()
)
.userDetailsService(userDetailsService(dataSource(), passwordEncoder())); // Explicitly set
return http.build();
}
}
}Testing Database Auth
Once your application is running, open your browser and navigate to a secured endpoint (e.g., /hello in our example).
You should be redirected to the login page. Try logging in with the credentials inserted into the database:
- Username:
user, Password:password - Username:
admin, Password:adminpass
Successful login means your database integration is working!
Database Auth Check
Which Spring Security component is essential for loading user data from a database?
Recap & Next Steps
Great job! You've successfully learned how to integrate Spring Security with a database.
- We understood the benefits of database-backed user management.
- We explored basic user table schemas.
- We saw how to use
UserDetailsService(specificallyJdbcUserDetailsManager) and aPasswordEncoderwith a database. - We configured Spring Security to use these components.
This is a foundational step for building robust, secure applications. Next, you'll dive deeper into authorization to control what authenticated users can do!
Frequently asked questions
Is the “Database User Management Integration” lesson free?
Yes — the full text of “Database User Management Integration” is free to read here on the web, and the Spring Security 6 & JWT Authentication course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Spring Security 6 & JWT Authentication course, upgrade to CoddyKit PRO.
What will I learn in “Database User Management Integration”?
Integrate Spring Security with a database to manage and authenticate users stored in a persistent data source. You practise Spring Security 6 & JWT Authentication with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Spring Security 6 & JWT Authentication?
No prior experience is required. Spring Security 6 & JWT Authentication on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Database User Management Integration” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Spring Security 6 & JWT Authentication lesson?
Yes. Every Spring Security 6 & JWT Authentication lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Custom UserDetailsService Implementation
- Understanding Password Encoders
- Database User Management Integration
- Role-Based Authorization with Granted Authorities