Packt+ | Advance your knowledge in tech

You're reading from Spring Security Secure your web applications, RESTful services, and microservice architectures

Product type Paperback

Published in Nov 2017

Publisher Packt

ISBN-13 9781787129511

Length 542 pages

Edition 3rd Edition

Languages

Java

Tools

Spring

Concepts

Cybersecurity

Authors (3):

Mick Knutson

Robert Winch

Mularien

View More author details

Table of Contents (25) Chapters

Title Page

Credits

About the Authors

About the Reviewers

www.Packtpub.com

Customer Feedback

Preface

1. Anatomy of an Unsafe Application FREE CHAPTER

2. Getting Started with Spring Security

3. Custom Authentication

4. JDBC-Based Authentication

5. Authentication with Spring Data

6. LDAP Directory Services

7. Remember-Me Services

8. Client Certificate Authentication with TLS

9. Opening up to OAuth 2

10. Single Sign-On with the Central Authentication Service

11. Fine-Grained Access Control

12. Access Control Lists

13. Custom Authorization

14. Session Management

15. Additional Spring Security Features

16. Migration to Spring Security 4.2

17. Microservice Security with OAuth 2 and JSON Web Tokens

18. Additional Reference Material

Getting started with the JBCP calendar sample code

Support for a custom schema

It's common for new users of Spring Security to begin their experience by adapting the JDBC user, group, or role mapping to an existing schema. Even though a legacy database doesn't conform to the expected Spring Security schema, we can still configure JdbcDaoImpl to map to it.

We will now update Spring Security's JDBC support to use our existing CalendarUser database along with a new calendar_authorities table.

We can easily change the configuration of JdbcUserDetailsManager to utilize this schema and override Spring Security's expected table definitions and columns, which we're using for the JBCP calendar application.

Determining the correct JDBC SQL queries

The JdbcUserDetailsManager class has three SQL queries that have a well-defined parameter and a set of returned columns. We must determine the SQL that we'll assign to each of these queries, based on the intended functionality. Each SQL query used by JdbcUserDetailsManager takes the username presented at login...