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
{{ message }}
This repository was archived by the owner on Jan 23, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+6-11Lines changed: 6 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -16,21 +16,16 @@ For more information about how the protocols work in this scenario and other sce
16
16
Getting started is simple! To run this sample you will need:
17
17
- Install .NET Core for Windows by following the instructions at [dot.net/core](https://dot.net/core), which will include Visual Studio 2015 Update 3.
18
18
- An Internet connection
19
-
- An Azure subscription (a free trial is sufficient)
20
-
21
-
Every Azure subscription has an associated Azure Active Directory tenant. If you don't already have an Azure subscription, you can get a free subscription by signing up at [https://azure.microsoft.com](https://azure.microsoft.com). All of the Azure AD features used by this sample are available free of charge.
19
+
- An Azure Active Directory (Azure AD) tenant. For more information on how to get an Azure AD tenant, please see [How to get an Azure AD tenant](https://azure.microsoft.com/en-us/documentation/articles/active-directory-howto-tenant/)
20
+
- A user account in your Azure AD tenant. This sample will not work with a Microsoft account, so if you signed in to the Azure portal with a Microsoft account and have never created a user account in your directory before, you need to do that now.
### Step 2: Create a user account in your Azure Active Directory tenant
30
-
31
-
If you already have a user account in your Azure Active Directory tenant, you can skip to the next step. This sample will not work with a Microsoft account, so if you signed in to the Azure portal with a Microsoft account and have never created a user account in your directory before, you need to do that now. If you create an account and want to use it to sign-in to the Azure portal, don't forget to add the user account as a co-administrator of your Azure subscription.
32
-
33
-
### Step 3: Register the sample with your Azure Active Directory tenant
28
+
### Step 2: Register the sample with your Azure Active Directory tenant
34
29
35
30
There are two projects in this sample. Each needs to be separately registered in your Azure AD tenant.
36
31
@@ -57,7 +52,7 @@ There are two projects in this sample. Each needs to be separately registered i
57
52
9. From the Settings menu, choose **Keys** and add a key - select a key duration of either 1 year or 2 years. When you save this page, the key value will be displayed, copy and save the value in a safe location - you will need this key later to configure the project in Visual Studio - this key value will not be displayed again, nor retrievable by any other means, so please record it as soon as it is visible from the Azure Portal.
58
53
10. Configure Permissions for your application - in the Settings menu, choose the 'Required permissions' section, click on **Add**, then **Select an API**, and type 'TodoListService' in the textbox. Then, click on **Select Permissions** and select 'Access TodoListService'.
59
54
60
-
### Step 4: Configure the sample to use your Azure AD tenant
55
+
### Step 3: Configure the sample to use your Azure AD tenant
61
56
62
57
#### Configure the TodoListService project
63
58
@@ -76,7 +71,7 @@ There are two projects in this sample. Each needs to be separately registered i
76
71
6. If you changed the base URL of the TodoListWebApp sample, find the `PostLogoutRedirectUri` property and replace the value with the new base URL of the sample.
77
72
8. Find the `TodoListResourceId` property and replace the value with the App ID URI registered for the TodoListService, for example `https://<your_tenant_name>/TodoListService`.
78
73
79
-
### Step 5: Trust the IIS Express SSL certificate
74
+
### Step 4: Trust the IIS Express SSL certificate
80
75
81
76
Since the web API is SSL protected, the client of the API (the web app) will refuse the SSL connection to the web API unless it trusts the API's SSL certificate. Use the following steps in Windows Powershell to trust the IIS Express SSL certificate. You only need to do this once. If you fail to do this step, calls to the TodoListService will always throw an unhandled exception where the inner exception message is:
82
77
@@ -112,7 +107,7 @@ You can verify the certificate is in the Trusted Root store by running this comm
112
107
113
108
`PS C:\windows\system32> dir Cert:\LocalMachine\Root`
114
109
115
-
### Step 6: Run the sample
110
+
### Step 5: Run the sample
116
111
117
112
Clean the solution, rebuild the solution, and run it. You might want to go into the solution properties and set both projects as startup projects, with the service project starting first.
0 commit comments