Skip to main content

Abstract

As described in the previous chapter, OAuth 2.0 provides a framework for authorizing applications to call APIs, but isn’t designed for authenticating users to applications. The OpenID Connect (OIDC)1 protocol provides an identity service layer on top of OAuth 2.0, designed to allow authorization servers to authenticate users for applications and return the results in a standard way. Some implementations of OAuth 2.0 added proprietary additions to do this, but a standard solution was needed. In this chapter, we’ll describe how an application can use OIDC to authenticate a user.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 34.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    https://tools.ietf.org/html/draft-ietf-oauth-security-topics-13#section-3.1.2

  2. 2.

    https://tools.ietf.org/html/draft-ietf-oauth-security-topics-13#section-3.1.2

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2019 Yvonne Wilson, Abhishek Hingnikar

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Wilson, Y., Hingnikar, A. (2019). OpenID Connect. In: Solving Identity Management in Modern Applications. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-5095-2_6

Download citation

Publish with us

Policies and ethics