快速入門：使用資料 API 建構器原則處理個別使用者資料

在這個快速入門中，你會使用 Quickstart 4 使用者驗證範例 DAB 政策來篩選每位登入使用者的資料。網頁應用程式會用 Microsoft Entra ID 登入使用者，將持有憑證傳送給資料 API 建構器（DAB），然後 DAB 在回傳 SQL 資料列前套用資料庫政策。

範例中使用單頁應用程式（SPA）中的Microsoft 驗證資源庫（MSAL）、DAB authenticated 角色，以及政策表達式 @item.Owner eq @claims.preferred_username。範例不使用用戶端秘密或自訂 API 程式碼。

先決條件

.NET 8 或更高
Docker 桌面
PowerShell
.NET Aspire 工具用於本地協調
Azure CLI 用於Microsoft Entra設定與Azure部署
如果你部署資料庫專案，請使用 SQL套件
具有建立 Azure SQL、Azure 容器應用程式、Azure Container Registry、Log Analytics 和資源群組權限的 Azure 訂用帳戶
建立或重用 Microsoft Entra 應用程式註冊的權限

樣本顯示的內容

一個靜態網頁應用程式，使用 MSAL 瀏覽器登入並自動重定向。
網頁應用程式的 SPA 應用程式註冊，以及供 DAB 使用的 API 應用程式註冊。
供瀏覽器在進行 DAB 呼叫時要求的委派 API 範圍權限。
從網頁應用程式對 DAB 發出的持有者權杖呼叫。
DAB 設定為使用 Microsoft Entra ID EntraId 驗證提供者。
使用 authenticated 角色的 DAB 實體權限。
DAB 資料庫政策會依據登入使用者的聲明來過濾資料列。
從 DAB 到本地 SQL Server 開發容器的 SQL 認證。
透過系統指派的管理身份，無需密碼即可存取 Azure SQL。
DAB 中可進行逐用戶資料過濾，無需自訂 API 程式碼或用戶端秘密。

身份驗證流程

跳	本地驗證	Azure 身份驗證
使用者對網頁應用程式	具備自動重新導向功能的 Microsoft Entra ID	Microsoft Entra ID 與自動重定向
網頁應用程式轉 API	持有者令牌	持有者令牌
API 角色	`authenticated`	`authenticated`
API 轉 SQL	帶有 DAB 政策的 SQL 認證	系統指派管理身份與 DAB 政策

與系列比較

Step	改變了什麼
上一個	Add a Microsoft Entra provider 會驗證代幣，但仍允許匿名實體存取。
本快速入門	需要 MSAL 登入，將承載代幣傳送至 DAB，並以 DAB 資料庫政策過濾資料列。
下一步	使用 SQL 列層級的安全措施，將每個使用者的過濾從 DAB 轉移到 SQL。

原則

DAB 將此資料庫政策套用於受保護實體的行動。

@item.Owner eq @claims.preferred_username

該原則允許已登入的使用者僅能存取其中 Owner 欄符合該使用者 preferred_username 宣告的資料列。從受保護的實體中移除 anonymous 角色，讓匿名對 REST 和 GraphQL 發出的請求會回傳 401。

{
  "entities": {
    "Todos": {
      "permissions": [
        {
          "role": "authenticated",
          "actions": [
            {
              "action": "read",
              "policy": {
                "database": "@item.Owner eq @claims.preferred_username"
              }
            },
            {
              "action": "update",
              "policy": {
                "database": "@item.Owner eq @claims.preferred_username"
              }
            },
            {
              "action": "delete",
              "policy": {
                "database": "@item.Owner eq @claims.preferred_username"
              }
            }
          ]
        }
      ]
    }
  }
}

請使用範例

複製樣本庫。

git clone https://github.com/Azure-Samples/dab-2.0-quickstart-web_entra-api_entra-db_entra-api_rls.git
cd dab-2.0-quickstart-web_entra-api_entra-db_entra-api_rls

恢復本地工具。

dotnet tool restore

登入Azure。

az login

在本機上執行範例。

dotnet run --project aspire-apphost

第一次執行時，Aspire 會檢查 Microsoft Entra 設定。若缺少設定值，範例可互動執行 azure-infra/entra-setup.ps1 。設定腳本會建立或設定應用程式註冊、更新 web-app/config.js 與 data-api/dab-config.json，並啟動本地資源。

這個網頁應用程式會將使用者重新導向到 Microsoft 登入。登入後，API 呼叫會包含承載憑證，每位使用者只會看到與其 preferred_username 主張相符的列。

將範例部署到 Azure。

pwsh ./azure-infra/azure-up.ps1

部署腳本會為 Azure SQL 和 Azure 容器應用程式提供資源，用於 DAB、網頁應用程式、模型上下文協定（MCP）檢查器及 SQL 指揮官。它也會以系統指派的管理身份配置 DAB 容器應用程式，並在部署期間執行 Microsoft Entra 設定。

完成後清理 Azure 資源和應用程式註冊。

pwsh ./azure-infra/azure-down.ps1

清理程序會執行 Microsoft Entra 拆解指令碼。如果你需要另外移除應用程式註冊，請從樣本中執行 azure-infra/entra-teardown.ps1 。

關鍵檔案

路徑	Purpose
`data-api/dab-config.json`	定義 `EntraId` 提供者、 `authenticated` 角色及資料庫政策。
`web-app/auth.js`	配置 MSAL、自動重定向、憑證擷取及登出操作。
`web-app/index.html`	載入 MSAL 瀏覽器支援並顯示已認證的 UI 元素。
`web-app/app.js`	驗證後初始化應用程式並更新登入狀態。
`web-app/dab.js`	在 DAB 呼叫中傳送 `Authorization: Bearer <token>` 標頭。
`web-app/config.js`	儲存 MSAL 的租戶 ID、SPA 用戶端 ID 及 API 範圍。

使用 GitHub Copilot 來重現這個範例

在 Visual Studio Code 中開啟你想建立範例的工作區，將 GitHub Copilot 切換成代理模式，然後貼上這個提示。

You are GitHub Copilot running in agent mode. Recreate the Data API builder Quickstart 4 User Authentication with DAB Policies sample as a complete, runnable project in the current VS Code workspace under `quickstart-04-dab-policies`. Build a static SPA with MSAL browser sign-in, DAB with Microsoft Entra bearer-token validation, a DAB database policy for per-user rows, local SQL Server with SQL authentication, Azure SQL with managed identity, REST, GraphQL, MCP, .NET Aspire, SQL Commander, MCP Inspector, and Azure Container Apps deployment scripts. DAB is the only API, GraphQL, and MCP layer over SQL. Do not create custom API code. Do not create or use a client secret for this quickstart.

Source repository: https://github.com/Azure-Samples/dab-2.0-quickstart-web_entra-api_entra-db_entra-api_rls. If internet access is available, inspect or clone this repository before you create files. Reuse and adapt its files as closely as possible, especially `web-app/`, `data-api/`, `database/`, `aspire-apphost/`, `mcp-inspector/`, `azure-infra/`, scripts, and README patterns. The goal is to implement the published quickstart, not to invent a different sample. If the repository differs from this prompt or the current Data API builder docs, prefer the current docs for product behavior.

Minimize user interaction. Use the defaults in this prompt and make reasonable best guesses for noncritical choices. Do not ask for a root folder or project folder name; use the current VS Code workspace and the default subfolder. Ask only when you need approval for resource changes, secrets, permissions, materially higher cost, external account choices, or an ambiguous requirement that affects the architecture.

Start with a short plan and proceed with safe defaults before you create files or run commands. Use the default `Owner nvarchar(256)` schema, `@claims.preferred_username` policy, and `api://<api-app-id>/access` scope unless the user explicitly asks for different values. Ask only these questions if the values aren't already available from the environment or prior context:

- Which Azure subscription, primary region, fallback region, resource group, and tenant should the sample use? Default fallback region: `westus2` if the primary region can't provision Azure SQL or Container Apps.
- Should I create new app registrations for the SPA and API or reuse existing registrations?
- Do you approve creating billable Azure resources and Microsoft Entra app registrations if deployment starts?

After the answers, show a checklist and ask for approval before implementation. Include phases for local scaffold, Entra setup, local validation, Azure infrastructure, Azure validation, and cleanup. Do not run `az`, `az ad`, or Azure deployment commands that create or change resources until the user explicitly approves the exact command set.

After approval, continue working without asking status-check questions. If a command, build, container, endpoint, or validation step fails, inspect the error, adjust the project, rerun the step, and continue. Keep iterating until the sample runs end-to-end or you hit a blocker that requires user action.

Use cost-first Azure defaults. Choose the cheapest option that satisfies the quickstart requirements: use a free Azure SQL database offer when the subscription and region support it; otherwise choose the lowest-cost SQL option that supports managed identity and Microsoft Entra validation. Use Azure Container Apps consumption, minimal CPU and memory, Basic Azure Container Registry, minimal Log Analytics retention, and no always-on or dedicated plans unless required. Prioritize finishing the project. Treat regional provisioning limits as expected adjustment points, not failures: if the primary region can't provision a required service or free SQL option, use the approved fallback region such as `westus2`, and continue the deployment. Ask the user only when both the primary and fallback regions can't satisfy the requirements, when a change would materially increase cost, when a new permission is required, or when you need approval for Azure commands that create or change resources beyond the already-approved plan. Keep every resource minimal, but make the web interface neat and approachable: small code footprint, responsive layout, clear status messages, accessible labels, and simple styling that is polished rather than austere.

Verify prerequisites and report only missing items: .NET SDK, Docker Desktop running, PowerShell, Azure CLI signed in, permission to use `az ad`, `sqlpackage`, .NET Aspire tooling, and the DAB CLI. Use these docs while building:

- DAB CLI reference: https://learn.microsoft.com/azure/data-api-builder/command-line/
- `dab add` policies: https://learn.microsoft.com/azure/data-api-builder/command-line/dab-add
- `dab validate`: https://learn.microsoft.com/azure/data-api-builder/command-line/dab-validate
- DAB MCP overview: https://learn.microsoft.com/azure/data-api-builder/mcp/overview
- Microsoft Entra authentication in DAB: https://learn.microsoft.com/azure/data-api-builder/concept/security/authenticate-entra

Create this structure under the sample folder:

- `azure-infra/` for Bicep, `azure-up.ps1`, `azure-down.ps1`, `entra-setup.ps1`, `entra-teardown.ps1`, and post-provision scripts.
- `data-api/` for `dab-config.json` and a DAB Dockerfile that bakes the config into the image for Azure.
- `database/` for a SQL Database Project or idempotent SQL scripts with seed rows for at least two owners.
- `web-app/` for static HTML, CSS, and JavaScript with MSAL browser support.
- `aspire-apphost/` for the .NET Aspire AppHost.
- `mcp-inspector/` for MCP Inspector notes or container assets.

Handle generated values first. Add `.env`, `**/bin`, and `**/obj` to `.gitignore` before writing secrets or local configuration. Use `MSSQL_CONNECTION_STRING`, `ENTRA_TENANT_ID`, `ENTRA_AUDIENCE`, `ENTRA_ISSUER`, `SPA_CLIENT_ID`, and `API_SCOPE`. Never print tokens or secret values. Use `@env(...)` placeholders in `dab-config.json` where practical.

Configure DAB CORS before you start or deploy the web app. Do not leave `runtime.host.cors.origins` as `[]`. Set it to include the exact web app origins, including scheme and port: the local Aspire web origin, such as `http://localhost:5173`, and the deployed Azure Container Apps web FQDN if Azure deployment is approved. Keep `allow-credentials` set to `false` because this SPA sends bearer tokens, not browser credentials or cookies. Direct REST, GraphQL, or Swagger requests can succeed even when the browser blocks JavaScript fetch calls, so browser-origin CORS must be configured and validated separately.

Use this DAB CLI workflow and validate after each config change:

```dotnetcli
dab init --database-type mssql --connection-string "@env('MSSQL_CONNECTION_STRING')" --auth.provider EntraID --auth.audience "@env('ENTRA_AUDIENCE')" --auth.issuer "@env('ENTRA_ISSUER')" --host-mode Development --rest.enabled true --graphql.enabled true --mcp.enabled true
dab add Todos --source dbo.Todos --source.type table --permissions "authenticated:read,update,delete" --policy-database "@item.Owner eq @claims.preferred_username" --mcp.dml-tools true
dab validate --config data-api/dab-config.json
```

Use this DAB policy shape if you write the config directly. Remove the `anonymous` role from protected entities so anonymous REST, GraphQL, and MCP calls to those entities are denied.

```json
{
  "role": "authenticated",
  "actions": [
    { "action": "read", "policy": { "database": "@item.Owner eq @claims.preferred_username" } },
    { "action": "update", "policy": { "database": "@item.Owner eq @claims.preferred_username" } },
    { "action": "delete", "policy": { "database": "@item.Owner eq @claims.preferred_username" } }
  ]
}
```

Implement the SPA with MSAL browser. `web-app/dab.js` must send bearer tokens to DAB on every protected request.

```javascript
export async function getAuthHeaders() {
  const token = await acquireAccessToken();
  return { Authorization: `Bearer ${token}` };
}
```

Use these Aspire patterns from the quickstart skills. Use `.WaitForCompletion(sqlDatabaseProject)` for DAB and SQL Commander when a SQL project deploys schema.

```csharp
var dabServer = builder.AddContainer("data-api", "azure-databases/data-api-builder", "latest")
    .WithImageRegistry("mcr.microsoft.com")
    .WithBindMount(new FileInfo("data-api/dab-config.json").FullName, "/App/dab-config.json", isReadOnly: true)
    .WithEnvironment("MSSQL_CONNECTION_STRING", sqlDatabase)
    .WithEnvironment("ENTRA_AUDIENCE", entraAudience)
    .WithEnvironment("ENTRA_ISSUER", entraIssuer)
    .WithHttpEndpoint(targetPort: 5000, name: "http")
    .WithHttpHealthCheck("/health")
    .WaitForCompletion(sqlDatabaseProject);
```

Add SQL Commander with image `jerrynixon/sql-commander:latest`, env var `ConnectionStrings__db`, and a connection string that includes `TrustServerCertificate=true`.

```csharp
var sqlCommander = builder.AddContainer("sql-cmdr", "jerrynixon/sql-commander", "latest")
    .WithImageRegistry("docker.io")
    .WithHttpEndpoint(targetPort: 8080, name: "http")
    .WithEnvironment("ConnectionStrings__db", sqlDatabase)
    .WithHttpHealthCheck("/health")
    .WaitForCompletion(sqlDatabaseProject);
```

Add MCP Inspector with Streamable HTTP transport and omit auth only for local development.

```csharp
var mcpInspector = builder.AddMcpInspector("mcp-inspector")
    .WithMcpServer(dabServer, transportType: McpTransportType.StreamableHttp)
    .WithEnvironment("DANGEROUSLY_OMIT_AUTH", "true")
    .WaitFor(dabServer);
```

For Azure, configure the DAB Container App with a system-assigned managed identity and bake `dab-config.json` into the DAB image. Replace web URL and CORS placeholders before image build. Do not rely on volume mounts in Azure Container Apps.

Validate before reporting success:

- `dab validate --config data-api/dab-config.json` exits with code 0.
- `dotnet run --project aspire-apphost` starts the complete local environment.
- A direct database query confirms the seeded table exists and contains rows for at least two owners.
- DAB `/health` returns a 2xx response.
- The web site returns a successful HTTP response.
- A browser-origin request from each web app origin receives an `Access-Control-Allow-Origin` response header that matches that origin.
- Anonymous REST and GraphQL requests to protected entities return `401`.
- Signed-in REST and GraphQL calls include bearer headers and return only rows where `Owner` equals the selected claim.
- Two different users see disjoint row sets.
- The DAB configuration uses the `authenticated` role with DAB database policies and no client secret.
- MCP Inspector can connect to DAB MCP and respects authenticated access for protected entities.
- SQL Commander opens and shows seeded tables for at least two owners.
- In Azure, the DAB Container App has a system-assigned managed identity and Container Apps are healthy.

Do not report final URLs, asset locations, or a success summary until you directly verify database connectivity and query results, a 2xx DAB health response, and a successful web site response. This validation ensures the sample works without requiring the developer to check.

意見反應

此頁面對您有幫助嗎？

Last updated on 2026-06-04