Skip to content

Latest commit

 

History

History
54 lines (33 loc) · 3.22 KB

File metadata and controls

54 lines (33 loc) · 3.22 KB

Day 1 - Challenge 02 - Add sign-in with Azure AD Identity to an ASP.NET Core web app

< Previous Challenge - Home - Next Challenge >

Introduction

As mentioned in the previous challenge, the Product Owner is willing to use a cloud identity solution for their internal web applications. Now it’s the time to continue you investigation and run a Proof of Concept (POC).

Description

In the previous challenge you have completed the setup of your tenant and you figured out that you have to create an Azure AD Application registration in order to proceed with the PoC. You found a very good QuickStart reference with a sample ASP.Net Core web application which will help you speed up the process. The link to the QuickStart can be found in the Learning Resources below.

Remember, the scope of the PoC is to allow your corporate users to login in to your application.

After completing the QuickStart guide and you run the application locally, you need to get familiar with the identity concepts. Hence you have to go through the learning resources and explain to your coach the following:

  • Differences between Single Tenant and Multi-tenant app types
  • Scopes and permissions
  • Permission types
  • User Consent and Admin Consent

Success Criteria

  • Demonstrate that you have configured the Application which has as an audience all the accounts in your directory only.
  • Demonstrate that you can login with HomeUserA account in your web application locally.
  • Briefly explain the differences between Single Tenant and Multi-tenant app types.
  • Explain what is the usage of scopes and permissions.
  • Explain what are the permission types.
  • Explain what is User Consent and Admin Consent.
  • (Optional) Explain the Application types options (SPA, web app, desktop app, daemon app) by specifying what authentication flow you will use for every option.

Tips

You should configure the Application Registration in your “HomeTenant”

You can configure the Redirect URIs after deploying your application.

You can limit the logins by using incognito mode and private browsing by logging in with different user accounts.

When you login with the user created, you will be prompt to provide more information to keep your account secure (required for MFA). Select the option Skip for now (14 days until this is required)

Learning Resources

Quickstart: Sign in users in web apps using the auth code flow

Single and multi-tenant apps

Scopes and Permissions

Permission types

Consent Types - User Consent and Admin Consent

Application Type Options (Optional)