Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Keycloak - Identity and Access Management for Modern Applications

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

Arrow left icon
Product type Paperback
Published in Jun 2021
Publisher Packt
ISBN-13 9781800562493
Length 362 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Pedro Igor Silva Pedro Igor Silva
Author Profile Icon Pedro Igor Silva
Pedro Igor Silva
Stian Thorgersen Stian Thorgersen
Author Profile Icon Stian Thorgersen
Stian Thorgersen
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

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

Securing the database

Keycloak stores a lot of sensitive data in its database, which makes it especially important to secure it, thus preventing attackers from accessing or modifying the databases.

Some examples of the data Keycloak stores includes the following:

  • Realm configuration
  • Users
  • Clients

If your database became compromised, we must consider some examples of what could happen if an attacker were able to read your data:

  • An attacker would get access to details about your employees or customers. The impact of this would depend on how much personal information you store about your users, but even a list of email addresses is valuable to an attacker.
  • An attacker would get access to user credentials. Even though passwords are stored as one-way salted hashes in the database, the attacker may be able to crack some of the less secure passwords.
  • If you are not using a vault or keystore, an attacker would have access to any secrets stored in...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime