You're reading from Keycloak - Identity and Access Management for Modern Applications Harness the power of Keycloak, OpenID Connect, and OAuth 2.0 protocols to secure applications

Product type Paperback

Published in Jun 2021

Publisher Packt

ISBN-13 9781800562493

Length 362 pages

Edition 1st Edition

Tools

Docker

Concepts

System Administration

Authors (2):

Pedro Igor Silva

Stian Thorgersen

View More author details

Table of Contents (21) Chapters

Preface

1. Section 1: Getting Started with Keycloak

2. Chapter 1: Getting Started with Keycloak FREE CHAPTER

3. Chapter 2: Securing Your First Application

4. Section 2: Securing Applications with Keycloak

5. Chapter 3: Brief Introduction to Standards

6. Chapter 4: Authenticating Users with OpenID Connect

7. Chapter 5: Authorizing Access with OAuth 2.0

8. Chapter 6: Securing Different Application Types

9. Chapter 7: Integrating Applications with Keycloak

10. Chapter 8: Authorization Strategies

11. Section 3: Configuring and Managing Keycloak

12. Chapter 9: Configuring Keycloak for Production

13. Chapter 10: Managing Users

14. Chapter 11: Authenticating Users

15. Chapter 12: Managing Tokens and Sessions

16. Chapter 13: Extending Keycloak

17. Section 4: Security Considerations

18. Chapter 14: Securing Keycloak and Applications

19. Assessments

20. Other Books You May Enjoy

Enabling clustering

Most of the time, you will be running a Keycloak cluster when going for production. To respect some key non-functional aspects, as well as the Service-Level Agreements (SLAs) defined for your services, enabling clustering is crucial.

In terms of availability, clustering allows you to run multiple Keycloak instances, possibly in different availability zones, so that uptime is not impacted if nodes go down.

From a scalability perspective, clustering allows you to scale your nodes up and down according to the load on your system, helping to keep a consistent response time and throughput.

In terms of failover, a cluster helps you to survive failures when nodes are failing, therefore preventing data loss (mainly that kept in caches) as well as avoiding impacts on general availability.

Keycloak is designed for high availability, where, in addition to the persistent data kept in the database, it also uses a cache layer to replicate and keep state in-memory...