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

Understanding the Discovery endpoint

The OIDC Discovery specification is an important aspect of both the interoperability and usability of OIDC Relying Party libraries. Without this specification, you would be required to do a lot of manual configuration in your applications to be able to authenticate with an OpenID Provider (more information on OpenID Providers can be found in Chapter 3, Brief Introduction to Standards).

It is an optional specification that an OpenID Provider can decide if it wants to implement or not. Luckily, most OpenID Providers, including Keycloak, implement this specification.

By simply knowing the base URL (often referred to as the issuer URL) for your OpenID Provider, a Relying Party can discover a lot of useful information about the provider. It does this by loading what is called the OpenID Provider Metadata from a standard endpoint, namely <base URL>/.well-known/openid-configuration.

To better understand the OpenID Provider Metadata, open...