Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
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

Chapter 6

  1. As an SPA is running in the browser, it cannot use a confidential client directly, which results in a greater risk if a refresh token is leaked. For this reason, it is more secure to have a backend running in a web server that can use a confidential client and store tokens on the server side.
  2. No, any type of application can use OAuth 2.0 through an external user agent to obtain an access token, and many different types of services have support for bearer tokens.
  3. An application should never collect user credentials directly as this increases the chance of credentials being leaked, and provides the application with full access to the user account. For this reason, native and mobile applications should use an external user agent to authenticate with Keycloak.
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
Banner background image