You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-9Lines changed: 12 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,14 +36,14 @@ In this tutorial, you will learn, incrementally, how to add sign-in users to you
36
36
37
37
### Details of the phases
38
38
39
-
1. The first phase is to [add sign-in to your Web App](1-WebApp-OIDC) leveraging the Microsoft identity platform for developers (fomerly Azure AD v2.0). You'll learn how to use the ASP.NET Core OpenID Connect (OIDC) middleware itself leveraging [Microsoft Identity Model extensions for .NET](https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/wiki) to protect your Web App.
39
+
1. The first phase is to [add sign-in users to your Web App](1-WebApp-OIDC) leveraging the Microsoft identity platform for developers (formerly Azure AD v2.0). You'll learn how to use the ASP.NET Core OpenID Connect (OIDC) middleware itself leveraging [Microsoft Identity Model extensions for .NET](https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/wiki) to protect your Web App.
Depending on your business needs, you have the flexibility to decide which audience to sign-in to your application:
44
44
1. If you are a Line of Business (LOB) developer, you'll want to [sign-in users in your organization](./1-WebApp-OIDC/1-1-MyOrg) with their work or school accounts.
45
45
1. If you are an ISV, you'll want to [sign-in users in any organization](./1-WebApp-OIDC/1-2-AnyOrg), still with their work or school accounts.
46
-
1. If you are an ISV targetting both organizations and individuals, you'll want to [sign-in users with their work and school accounts or Microsoft personal accounts](./1-WebApp-OIDC/1-3-AnyOrgOrPersonal).
46
+
1. If you are an ISV targeting both organizations and individuals, you'll want to [sign-in users with their work and school accounts or Microsoft personal accounts](./1-WebApp-OIDC/1-3-AnyOrgOrPersonal).
47
47
1. LOB developer or ISV, if you target organizations (work or school accounts), you can also enable your application to sign-in users in [national and sovereign clouds](./1-WebApp-OIDC/1-4-Sovereign).
48
48
1. If you are a business wanting to connect with your customers, or with small business partners, you might also want to [sign-in users with their social identities](./1-WebApp-OIDC/1-5-B2C) using Microsoft Azure AD B2C.
49
49
1. Finally, you'll want to let users [sign-out](./1-WebApp-OIDC/1-6-SignOut) of our application, or globally of the browser.
@@ -57,27 +57,31 @@ In this tutorial, you will learn, incrementally, how to add sign-in users to you
57
57
1. Using the [authorization code flow](2-WebApp-graph-user/2-1-Call-MSGraph), initiated by ASP.NET Core, but completed by Microsoft Authentication Library for .NET (MSAL.NET)
58
58
2. Learn how to [customize the token cache serialization](2-WebApp-graph-user/2-2-TokenCache)
59
59
) with different technologies depending on your needs (in memory cache, Session token cache, SQL Cache, Redis Cache)
60
-
3. Learn the [**coming soon**][best practices and practices to avoid](./2-WebApp-graph-user/2-3-Best-Practices) when calling an API.
60
+
3. Learn the [**Planned**][best practices and practices to avoid](./2-WebApp-graph-user/2-3-Best-Practices) when calling an API.
61
61
62
62
3. Your Web App might also want to call other Web APIs than Microsoft Graph.
63
63
64
64

65
65
66
-
Learn how to [call several Microsoft APIS](./3-WebApp-multi-APIs), feature conditional access and claims challenge:
66
+
Learn how to [call several Microsoft APIS](./3-WebApp-multi-APIs). This also explains how to handle conditional access, incremental consent and claims challenge:
67
67
68
68
1. the Azure Storage API. This is the opportunity to learn about incremental consent, and conditional access, and how to process them.
69
69
2. the Azure ARM API. This is the opportunity to learn about admin consent.
70
70
71
+
> Note that this phase, contrary to the others, requires you to have an Azure Subscription
72
+
71
73
4. Then you might yourself have written a Web API, and want to call it from your Web App.
72
74
73
75

74
76
75
-
5. Once you know how to sign-in users and call Web APIs from your Web App, you might want to restrict part of the application depending on the user having a role in the application or belonging to a group. So far you've learnt how to add and process authentication. Now learn how to [add authorization to your Web application](./5-WebApp-AuthZ):
77
+
Learn how to update your Web App to [call your own web api](./4-WebApp-your-API)
78
+
79
+
5. Once you know how to sign-in users and call Web APIs from your Web App, you might want to restrict part of the application depending on the user having a role in the application or belonging to a group. So far you've learnt how to add and process authentication. Now learn how to [add authorization to your Web application](./5-WebApp-AuthZ), restricting part of it to users
2.[with Azure AD groups](./5-WebApp-AuthZ/5-2-Groups)
81
+
1.[based on their application roles](./5-WebApp-AuthZ/5-1-Roles)
82
+
2.[based on their belonging to Azure AD groups](./5-WebApp-AuthZ/5-2-Groups)
79
83
80
-
6.[Planned]Chances are that you want to [deploy your complete app to Azure](./6-Deploy-to-Azure). Learn how to do that, applying best practices:
84
+
6. Chances are that you want to [deploy your complete app to Azure](./6-Deploy-to-Azure). Learn how to do that, applying best practices:
81
85
82
86
1. Changing the app registration to add more ReplyUris
83
87
2. Using certificates instead of client secrets
@@ -96,7 +100,6 @@ This tutorial only covers the case the Web App calls a Web API on behalf of a us
96
100
### Pre-requisites
97
101
98
102
- Install .NET Core for Windows by following the instructions at [dot.net/core](https://dot.net/core), which will include [Visual Studio 2017](https://aka.ms/vsdownload).
99
-
- An Internet connection
100
103
- An Azure Active Directory (Azure AD) tenant. For more information on how to get an Azure AD tenant, see [How to get an Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)
101
104
- A user account in your Azure AD tenant, or a Microsoft personal account
0 commit comments