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: data-explorer/kusto/api/monaco/host-web-ux-in-iframe.md
+19-11Lines changed: 19 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ The `workspace=<guid>` query parameter creates a separate workspace for the embe
33
33
34
34
### Handle authentication
35
35
36
-
When embedding the web UI, the hosting page is responsible for authentication. The following diagrams describe the authentication flow.
36
+
When you embed the web UI, the hosting page is responsible for authentication. The following diagrams describe the authentication flow.
37
37
38
38
:::image type="content" source="../media/host-web-ux-in-iframe/adx-embed-sequence-diagram.png" lightbox="../media/host-web-ux-in-iframe/adx-embed-sequence-diagram.png" alt-text="Diagram that shows the authentication flow for an embedded web U I iframe.":::
39
39
@@ -60,7 +60,7 @@ Use the following steps to handle authentication:
For example, the following function maps scopes based on the information in the table.
63
+
For example, the following function maps the scopes based on the information in the table.
64
64
65
65
```javascript
66
66
functionmapScope(scope) {
@@ -74,7 +74,7 @@ Use the following steps to handle authentication:
74
74
75
75
1. Get a [JWT access token](https://tools.ietf.org/html/rfc7519) from the [Perform Single Page Application (SPA) authentication](../rest/authenticate-with-msal.md#perform-single-page-application-spa-authentication) for the scope. This code replaces placeholder CODE-1.
76
76
77
-
For example, you can use @azure/MSAL-react to get the access token. The example uses the **mapScope**function you defined earlier.
77
+
For example, you can use `@azure/MSAL-react` to get the access token. The example uses the **mapScope**function you defined earlier.
78
78
79
79
```javascript
80
80
import { useMsal } from "@azure/msal-react";
@@ -91,7 +91,7 @@ Use the following steps to handle authentication:
91
91
```
92
92
93
93
> [!IMPORTANT]
94
-
> You can only use User Principal Name (UPN) for authentication, service principals are not supported.
94
+
> You can only use User Principal Name (UPN) for authentication, service principals aren't supported.
95
95
96
96
1. Post a **postToken** message with the access token. This code replaces placeholder CODE-2:
97
97
@@ -122,9 +122,15 @@ To embed a dashboard, a trust relationship must be established between the host'
122
122
1. Select **requiredResourceAccess**.
123
123
1. In the manifest, add the following entry:
124
124
125
+
> [!IMPORTANT]
126
+
> Replace `<RTD Metadata Service - Application ID>`with the application IDof the **RTD Metadata Service**. To get the application IDofthis service, follow these steps:
127
+
>- Sign in to the Azure portal.
128
+
>- In the search bar, enter **RTD Metadata Service**, and then select the **Service Principal**:**RTD Metadata Service**.
129
+
>- On the **Enterprise Application** page for**RTD Metadata Service**, note down the value of the **Application ID**.
@@ -189,7 +197,7 @@ A feature flag can be used in the URL as a query parameter. To disable adding ot
189
197
| f-ShowPersona | Show the user name from the settings menu, in the top-right corner. |true|
190
198
| f-UseMeControl | Show the user's account information | true |
191
199
| f-IFrameAuth | If true, the web explorer expects the iframe to handle authentication and provide a token via a message. This parameter is required for iframe scenarios. | false |
192
-
| f-PersistAfterEachRun | Usually, browsers persist in the unload event. However, the unload event isn't always triggered when hosting in an iframe. This flag triggers the **persisting local state**event after each query run. This limits any data loss that may occur, to only affect newquery text that has never run. |false|
200
+
| f-PersistAfterEachRun | Usually, browsers persist in the `unload` event. However, the `unload` event isn't always triggered when hosting in an iframe. This flag triggers the **persisting local state**event after each query run. This limits any data loss that may occur, to only affect newquery text that has never run. |false|
193
201
| f-ShowSmoothIngestion | If true, show the ingestion wizard experience when right-clicking on a database |true|
194
202
| f-RefreshConnection | If true, always refreshes the schema when loading the page and never depends on local storage |false|
195
203
| f-ShowPageHeader | If true, shows the page header that includes the Azure Data Explorer title and settings |true|
@@ -205,7 +213,7 @@ A feature flag can be used in the URL as a query parameter. To disable adding ot
205
213
| f-DisableDashboardDelete | IF true, hides the dashboard delete button | false |
206
214
| f-DisableTileRefresh | IF true, disables tiles refresh button in a dashboard | false |
207
215
| f-DisableDashboardAutoRefresh | IF true, disables tiles auto refresh in a dashboard | false |
208
-
| f-DisableExploreQuery | IF true, disables the explore query button of the tiles | false |
216
+
| f-DisableExploreQuery | IF true, disables the **Explore query** button of the tiles | false |
209
217
| f-DisableCrossFiltering | IF true, disables the cross filtering feature in dashboards | false |
210
218
| f-HideDashboardParametersBar | IF true, hides the parameters bar in a dashboard | false |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments