Book Image

Azure Active Directory for Secure Application Development

By : Sjoukje Zaal
Book Image

Azure Active Directory for Secure Application Development

By: Sjoukje Zaal

Overview of this book

Azure Active Directory for Secure Application Development is your one-stop shop for learning how to develop secure applications using modern authentication techniques with Microsoft Azure AD. Whether you’re working with single-tenant, multi-tenant, or line-of-business applications, this book contains everything you need to secure them. The book wastes no time in diving into the practicalities of Azure AD. Right from the start, you’ll be setting up tenants, adding users, and registering your first application in Azure AD. The balance between grasping and applying theory is maintained as you move from the intermediate to the advanced: from the basics of OAuth to getting your hands dirty with building applications and registering them in Azure AD. Want to pin down the Microsoft Graph, Azure AD B2C, or authentication protocol best practices? We’ve got you covered. The full range of Azure AD functionality from a developer perspective is here for you to explore with confidence. By the end of this secure app development book, you’ll have developed the skill set that so many organizations are clamoring for. Security is mission-critical, and after reading this book, you will be too.
Table of Contents (14 chapters)
Part 1: Getting Started with the Microsoft Identity Platform
Part 2: Authentication and Protocols
Part 3: Azure AD B2C

The OAuth 2.0 framework and its specifications

In the previous chapter, we briefly covered OAuth and why this protocol is well suited for modern applications. OAuth is an authorization framework that is specifically designed to meet the security scenarios that are required nowadays for authenticating users and connecting various services together.

The OAuth 2.0 authorization framework is a delegation protocol that provides the user with the ability to grant an application or service access to protected resources without impersonating the user and revealing their credentials. To do this, OAuth 2.0 introduces an authorization layer where the role of the client is separated from the role of the resource owner. The application can request authorization from the owner of the resource, and it will receive tokens that it can use to access those resources. This token represents delegated permissions to access the resource, without the need for the application to impersonate the user who...