Snabbstart: Använda sql-säkerhet på radnivå med Data API Builder

I den här snabbstarten använder du Quickstart 5 Row-Level Security-exempel för att framtvinga dataisolering per användare i SQL Server. Webbappen loggar in användare med Microsoft Entra ID, skickar en ägartoken till Data API Builder (DAB) och SQL-säkerhet på radnivå (RLS) filtrerar rader på databaslagret.

Exemplet använder Microsofts autentiseringsbibliotek (MSAL) i ett ensidesprogram (SPA), DAB-authenticated-rollen och SQL Server säkerhet på radnivå (RLS) med en predikatfunktion och säkerhetsprincip. DAB mappar den autentiserade användarens preferred_username anspråk till SQL SESSION_CONTEXToch SQL filtrerar rader från sessionskontexten. Exemplet använder inte DAB-databasprinciper per entitet eller anpassad API-kod.

Förutsättningar

• .NET 8 eller senare
• Docker Desktop
• PowerShell
• .NET Aspire verktyg för lokal orkestrering
• Azure CLI för Microsoft Entra konfiguration och Azure distribution
• sqlpackage om du distribuerar databasprojektet
• En Azure-prenumeration med behörighet att skapa Azure SQL, Azure Container Apps, Azure Container Registry, Log Analytics och en resursgrupp
• Behörighet att skapa eller återanvända Microsoft Entra appregistreringar

Vad exemplet visar

• En statisk webbapp som använder MSAL-webbläsarinloggning och automatisk omdirigering.
• En SPA-appregistrering för webbappen och en API-appregistrering för DAB.
• Ett delegerat API-omfång som webbläsaren begär för DAB-anrop.
• Bearer-token-anrop från webbappen till DAB.
• DAB har konfigurerats med autentiseringsprovidern Microsoft Entra ID EntraId.
• Entitetsbehörigheter för DAB som använder rollen authenticated.
• SQL Server RLS som filtrerar rader efter den inloggade användarens preferred_username anspråk.
• DAB-sessionskontext som mappar JSON-webbtokenanspråk (JWT) till SQL SESSION_CONTEXT.
• SQL-autentisering från DAB till den lokala SQL Server utvecklingscontainern.
• Lösenordslös DAB-åtkomst till Azure SQL via en systemtilldelad hanterad identitet.
• Datafiltrering per användare i SQL utan DAB-databasprinciper per entitet.

Autentiseringsflöde

Hoppa	Lokal autentisering	Azure-autentisering
Användare till webbapp	Microsoft Entra ID med automatisk omdirigering	Microsoft Entra ID med automatisk omdirigering
Webbapp till API	Bärartoken	Bärartoken
API-roll	authenticated	authenticated
API till SQL	SQL-autentisering med SQL RLS	Systemtilldelad hanterad identitet med SQL RLS

Jämför med serien

Step	Vilka ändringar
Previous	Använd DAB-policyer för användarspecifika data för att filtrera rader i DAB med policyuttryck.
Den här snabbstarten	Flyttar filtrering per användare till SQL RLS med hjälp av DAB-ifylld sessionskontext.
Nästa	Använd för autentisering låter Azure SQL autentisera den faktiska inloggade användaren.

RLS-princip

SQL Server framtvingar åtkomst på radnivå med en predikatfunktion och säkerhetsprincip.

CREATE FUNCTION dbo.UserFilterPredicate(@OwnerId sysname)
RETURNS TABLE WITH SCHEMABINDING AS
RETURN SELECT 1 AS IsVisible
WHERE @OwnerId = CAST(SESSION_CONTEXT(N'preferred_username') AS sysname);

CREATE SECURITY POLICY UserFilterPolicy
ADD FILTER PREDICATE dbo.UserFilterPredicate(Owner) ON dbo.Todos
WITH (STATE = ON);

DAB skickar autentiserade JWT-anspråk till SQL-sessionskontexten när data-source.options.set-session-context är true.

{
  "data-source": {
    "database-type": "mssql",
    "connection-string": "@env('MSSQL_CONNECTION_STRING')",
    "options": {
      "set-session-context": true
    }
  }
}

Databasen returnerar endast rader där Owner kolumnen matchar SESSION_CONTEXT(N'preferred_username'). DAB kan begära rader normalt; SQL framtvingar det slutliga filtret.

Viktigt!

Det här exemplet använder inte DAB-databasprinciper som @item.Owner eq @claims.preferred_username. SQL RLS äger radfiltret.

Använd exemplet

Klona exempellagringsplatsen.

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

Återställ lokala verktyg.

dotnet tool restore

Logga in på Azure.

az login

Kör exemplet lokalt.

dotnet run --project aspire-apphost

Vid första körningen kontrollerar Aspire konfigurationen för Microsoft Entra. Om konfigurationsvärden saknas erbjuder sig exemplet att köra Microsoft Entra installationsflödet interaktivt. Installationsskriptet skapar eller konfigurerar appregistreringar, uppdateringar web-app/config.js och data-api/dab-config.json, och startar de lokala resurserna.

Webbappen omdirigerar användare till Microsoft inloggning. Efter inloggning inkluderar API-anrop bearertoken, DAB mappar preferred_username till SQL-sessionskontexten och SQL RLS returnerar endast matchande rader.

Distribuera exemplet till Azure.

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

Distributionsskriptet etablerar Azure SQL och Azure Container Apps resurser för DAB, webbappen, MCP-inspektören (Model Context Protocol) och SQL Commander. Den konfigurerar också DAB-containerappen med en systemtilldelad hanterad identitet och körs azure-infra/post-provision.ps1 för att distribuera databasen, skapa den hanterade identitetsanvändaren, bevilja databasroller och verifiera RLS-konfigurationen.

Rensa Azure resurser och appregistreringar när du är klar.

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

Rensningsflödet tar bort Azure resurser och kör skriptet Microsoft Entra teardown. Om du behöver ta bort appregistreringar separat kör du borttagningsskriptet från exempelmappen azure-infra .

Nyckelfiler

Sökväg	Purpose
data-api/dab-config.json	Definierar providerEntraId, authenticated roll och set-session-context inställning.
database/Functions/UserFilterPredicate.sql	Definierar RLS-predikatfunktionen som jämför Owner med SESSION_CONTEXT(N'preferred_username').
database/Security/UserFilterPolicy.sql	Definierar säkerhetsprincipen för UserFilterPolicydbo.Todos.
web-app/auth.js	Konfigurerar MSAL, automatisk omdirigering, tokenförvärv och utloggningsåtgärden.
web-app/dab.js	Skickar Authorization: Bearer <token> rubriker med DAB-anrop.
web-app/config.js	Lagrar klientorganisations-ID, SPA-klient-ID, API-URL och API-omfång för MSAL.
azure-infra/post-provision.ps1	Distribuerar dacpac-filen, anger Microsoft Entra-administratören för Azure SQL, skapar användaren för hanterad identitet, tilldelar databasroller och uppdaterar inställningar för DAB och webbappen.

Använd GitHub Copilot för att återskapa det här exemplet

Öppna arbetsytan där du vill skapa exemplet i Visual Studio Code, växla GitHub Copilot till agentläge och klistra in den här uppmaningen.

You are GitHub Copilot running in agent mode. Recreate the Data API builder Quickstart 5 SQL Row-Level Security sample as a complete, runnable project in the current VS Code workspace under `quickstart-05-sql-row-level-security`. Build a static SPA with MSAL browser sign-in, DAB with Microsoft Entra bearer-token validation, SQL Server row-level security (RLS), 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 add DAB per-entity database policies; SQL RLS must enforce row filtering. 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-db_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) NOT NULL` schema, `api://<api-app-id>/access` scope, and `preferred_username` claim-to-session-context mapping 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?

If any artifact uses a different claim key, align all DAB config, SQL predicate, seed data, and validation steps to `preferred_username` and continue. Ask only if the intended claim mapping is ambiguous after inspecting the artifacts.

After the answers, show a checklist and ask for approval before implementation. Include phases for local scaffold, Entra setup, RLS schema, 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, Microsoft Entra validation, and SQL row-level security. 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 init` session context: https://learn.microsoft.com/azure/data-api-builder/command-line/dab-init
- `dab configure` session context: https://learn.microsoft.com/azure/data-api-builder/command-line/dab-configure
- `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

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.ps1`.
- `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 with `Functions/UserFilterPredicate.sql`, `Security/UserFilterPolicy.sql`, and 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')" --set-session-context true --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,create,update,delete" --mcp.dml-tools true
dab validate --config data-api/dab-config.json
```

Use this DAB data-source shape. `set-session-context` is required so DAB maps claims into SQL `SESSION_CONTEXT`.

```json
{
  "data-source": {
    "database-type": "mssql",
    "connection-string": "@env('MSSQL_CONNECTION_STRING')",
    "options": { "set-session-context": true }
  }
}
```

Create SQL RLS in the database project. The predicate must use the same claim name DAB sends to `SESSION_CONTEXT`; if any artifact uses a different key, align the artifacts to the approved claim mapping and continue. Ask the user only if the intended claim mapping is ambiguous.

```sql
CREATE FUNCTION dbo.UserFilterPredicate(@OwnerId sysname)
RETURNS TABLE WITH SCHEMABINDING AS
RETURN SELECT 1 AS IsVisible
WHERE @OwnerId = CAST(SESSION_CONTEXT(N'preferred_username') AS sysname);

CREATE SECURITY POLICY UserFilterPolicy
ADD FILTER PREDICATE dbo.UserFilterPredicate(Owner) ON dbo.Todos
WITH (STATE = ON);
```

Do not add `policy.database` filters to DAB entity permissions in this quickstart. SQL RLS is the authoritative filter. Remove the `anonymous` role from protected entities so anonymous REST, GraphQL, and MCP calls to those entities are denied.

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, deploy the dacpac before image validation, 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, contains rows for at least two owners, and has the RLS policy enabled.
- 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 reach DAB under the `authenticated` role.
- DAB sends `preferred_username` into SQL `SESSION_CONTEXT`.
- `SELECT name, is_enabled FROM sys.security_policies` shows `UserFilterPolicy` with `is_enabled = 1`.
- Two different users see different row sets when `Owner` values differ.
- The DAB configuration has `set-session-context` set to `true` and no per-entity database policies.
- MCP Inspector can connect to DAB MCP and respects authenticated access for protected entities.
- SQL Commander opens and shows seeded tables and the enabled RLS policy.
- 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.

Relaterat innehåll

• Snabbstart för Data API Builder
• Snabbstart: Använd vidarebefordrad autentisering med Data API Builder
• Snabbstart: Använd Data API Builder-principer för användarspecifika data
• Quickstart: Lägg till en Microsoft Entra-provider i Data API Builder
• Snabbstart: Använda hanterad identitet med Data API Builder
• Microsoft Entra ID-autentisering i Data API Builder
• DAB-konfigurationsfil
• Distribuera Data API builder till Azure Container Apps