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: 2-WebApp-graph-user/2-6-BFF-Proxy/README.md
+13-4Lines changed: 13 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,10 +71,19 @@ or download and extract the repository *.zip* file.
71
71
### Step 2: Navigate to project folder
72
72
73
73
```console
74
-
cd 2-WebApp-graph-user/2-6-BFF-Proxy
74
+
cd 2-WebApp-graph-user/2-6-BFF-Proxy/CallGraphBFF
75
75
```
76
76
77
-
### Step 3: Register the sample application(s) in your tenant
77
+
### Step 3. Trust development certificates
78
+
79
+
```console
80
+
dotnet dev-certs https --clean
81
+
dotnet dev-certs https --trust
82
+
```
83
+
84
+
For more information and potential issues, see: [HTTPS in .NET Core](https://docs.microsoft.com/aspnet/core/security/enforcing-ssl).
85
+
86
+
### Step 4: Register the sample application(s) in your tenant
78
87
79
88
There is one project in this sample. To register it, you can:
80
89
@@ -166,12 +175,12 @@ Open the project in your IDE (like Visual Studio or Visual Studio Code) to confi
166
175
1. Find the key `ClientId` and replace the existing value with the application ID (clientId) of `CallGraphBFF` app copied from the Azure portal.
167
176
1. Find the key `ClientSecret` and replace the existing value with the generated secret that you saved during the creation of `CallGraphBFF` copied from the Azure portal.
168
177
169
-
### Step 4: Running the sample
178
+
### Step 5: Running the sample
170
179
171
180
From your shell or command line, execute the following commands:
0 commit comments