빠른 시작: Data API Builder에서 대리 인증 사용

이 빠른 시작에서는 Quickstart 6 On-Behalf-Of Flow 샘플을 사용하여 사용자 위임 인증으로 DAB(Data API Builder)를 실행합니다. 웹앱은 Microsoft Entra ID 사용하여 사용자를 로그인하고, 전달자 토큰을 DAB로 보내고, DAB는 로그인한 사용자의 Azure SQL 토큰에 대한 각 토큰을 교환합니다.

로컬 SQL Server Microsoft Entra 토큰을 수락할 수 없기 때문에 샘플은 Azure SQL 사용합니다. SELECT SUSER_NAME()를 실행하는 WhoAmI 뷰는 SQL이 DAB 관리 ID가 아니라 실제 호출자를 확인한다는 것을 입증합니다.

사전 요구 사항

• .NET 8 이상
• Docker Desktop
• PowerShell
• 빌드 오케스트레이션을 위한 .NET Aspire 도구
• Microsoft Entra 설정 및 Azure 배포를 위한 Azure CLI
• 데이터베이스 프로젝트를 배포하는 경우 sqlpackage
• Azure SQL, Azure Container Apps, Azure Container Registry, Log Analytics 및 리소스 그룹을 만들 수 있는 권한이 있는 Azure 구독
• Microsoft Entra 앱 등록을 만들고, API 앱 클라이언트 암호를 만들고, 위임된 Azure SQL Database user_impersonation 권한을 추가하고, 관리자 동의를 부여할 수 있는 권한
• Azure SQL Microsoft Entra 관리자가 될 수 있는 Microsoft Entra 사용자 또는 그룹

샘플에 표시되는 내용

• MSAL 브라우저 로그인을 사용하는 정적 웹앱입니다.
• 웹 앱에서 DAB로의 베어러 토큰 호출
• Microsoft Entra ID EntraId 인증 공급자로 구성된 DAB입니다.
• OBO 토큰 교환용으로 구성된 DAB user-delegated-auth
• OBO 교환에 대한 클라이언트 암호를 사용하여 API 앱 등록
• 관리자 동의가 있는 Azure SQL Database 위임된 user_impersonation 권한
• User ID, Password 또는 Authentication 키워드가 없는 bare Azure SQL 연결 문자열.
• 익명 액세스 권한이 없는 인증된 DAB 엔터티입니다.
• 로그인한 호출자에 대한 Azure SQL 사용자가 포함되어 있습니다.
• SQL 호출자 ID를 검증하기 위해 SUSER_NAME()를 반환하는 WhoAmI 뷰입니다.
• azure-infra의 PowerShell 스크립트를 통한 Azure 배포 및 정리.

인증 흐름

홉	Authentication
사용자-웹앱	Microsoft Entra ID 사용하여 MSAL 브라우저 로그인
웹앱에서 DAB API로	DAB API 대상 그룹에 대한 전달자 토큰
DAB API 역할	authenticated
DAB에서 Azure SQL로	실제 로그인한 사용자에 대한 OBO 토큰

시리즈와 비교

Step	변경 내용
Previous	SQL에서 SQL 행 수준 보안 필터 행을 사용하지만 SQL은 여전히 DAB 서비스 ID를 인증합니다.
이 빠른 시작	OBO를 사용하여 Azure SQL 감사 및 사용자 인식 정책에 대한 실제 로그인 사용자를 인증합니다.
다음	OBO 인증 구성 은 OBO 구성 속성을 자세히 설명합니다.

Azure 전용 동작

OBO에는 Microsoft Entra 인증을 사용하는 Azure SQL 필요합니다. 로컬 SQL Server 컨테이너는 Microsoft Entra 토큰을 수락할 수 없으므로 전체 OBO 경로는 Azure 전용입니다.

DAB가 인증된 각 요청에 사용자별 OBO 토큰을 삽입할 수 있도록 bare Azure SQL 연결 문자열 사용합니다.

Server=tcp:<server>.database.windows.net,1433;Database=<database>;Encrypt=True;TrustServerCertificate=False;

OBO 연결 문자열 다음 값을 포함하지 마세요.

• User ID
• Password
• Authentication

중요합니다

연결 문자열 Authentication= 포함되는 경우 DAB가 액세스 토큰을 제공할 때 SQL 클라이언트 라이브러리는 요청을 거부합니다.

샘플 사용

샘플 리포지토리를 복제합니다.

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

로컬 도구를 복원합니다.

dotnet tool restore

Azure에 로그인합니다.

az login

샘플을 Azure에 배포하세요.

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

배포 스크립트는 DAB, 웹앱, MCP 검사기 및 SQL 사령관에 대한 Azure SQL 및 Azure Container Apps 리소스를 프로비전합니다. 또한 Microsoft Entra 설치 프로그램을 실행하고, API 앱 클라이언트 비밀을 만들고, 위임된 Azure SQL Database user_impersonation 권한을 추가하고, 관리자 동의를 부여하고, 데이터베이스를 배포하고, 포함된 사용자를 만들고, OBO용 DAB를 구성합니다.

배포 후 스크립트에서 인쇄한 웹앱 URL을 엽니다. 로그인하고 SQL Server 배지에 사용자 계정 이름이 표시되는지 확인합니다. 배지는 SELECT SUSER_NAME()로 뒷받침되는 WhoAmI 엔터티를 읽습니다.

익명 API 요청은 401 Unauthorized을 반환해야 합니다.

완료되면 Azure 리소스 및 앱 등록을 정리합니다.

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

키 파일

Path	Purpose
data-api/dab-config.json	user-delegated-auth을(를) 활성화하고, 캐시를 비활성화하고, EntraId을(를) 구성하고, WhoAmI 뷰 엔터티를 노출합니다.
database/Views/WhoAmI.sql	ID 확인을 위해 정의합니다 SELECT SUSER_NAME() AS UserName .
web-app/index.html	로그인한 사용자 및 SQL ID 배지를 표시합니다.
web-app/app.js	로그인, 페이지 업데이트 및 ID 새로 고침을 조정합니다.
web-app/dab.js	DAB에 Bearer 토큰 요청을 보내고 WhoAmI를 읽습니다.
azure-infra/entra-setup.ps1	Microsoft Entra 앱 등록을 만들고, API 클라이언트 비밀을 만들고, 위임된 Azure SQL Database user_impersonation 추가하고, 관리자 동의를 부여합니다.
azure-infra/resources.bicep	Azure 리소스를 정의하고 Azure SQL의 기본 연결 문자열과 OBO 설정을 DAB에 전달합니다.
azure-infra/post-provision.ps1	데이터베이스를 배포하고, Azure SQL Microsoft Entra 관리자를 설정하고, 포함된 사용자를 만들고, OBO 환경 값을 구성합니다.

GitHub Copilot 사용하여 이 샘플 다시 생성

Visual Studio Code 샘플을 만들 작업 영역을 열고 GitHub Copilot 에이전트 모드로 전환한 다음 이 프롬프트를 붙여넣습니다.

You are GitHub Copilot running in agent mode. Recreate the Data API builder Quickstart 6 On-Behalf-Of Flow sample as a complete Azure-only project in the current VS Code workspace under `quickstart-06-on-behalf-of`. Build a static SPA with MSAL browser sign-in, DAB with Microsoft Entra bearer-token validation and OBO user-delegated authentication, Azure SQL, REST, GraphQL, MCP, .NET Aspire build orchestration, SQL Commander, MCP Inspector, and Azure Container Apps deployment scripts. DAB is the only API, GraphQL, and MCP layer over SQL. SQL must authenticate the actual signed-in user, not the DAB managed identity or service principal.

Source repository: https://github.com/Azure-Samples/dab-2.0-quickstart-web_entra-api_entra-db_entra-obo. 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.

Azure-only constraint: do not build a local SQL Server OBO path. Local SQL Server cannot accept Microsoft Entra tokens. Use local tooling only for project generation, web app development, DAB config validation where possible, container builds, and database package builds.

Start with a short plan and proceed with safe defaults before you create files or run commands. Use the default `WhoAmI` view unless the user explicitly asks for additional schema. 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 SPA and API app registrations or reuse existing registrations?
- Confirm that the API app can use a client secret. OBO requires a confidential client.
- Confirm that the API app should receive Azure SQL Database delegated `user_impersonation` permission and admin consent.
- Which Microsoft Entra user or group should become the Azure SQL Microsoft Entra admin?
- Which signed-in users or groups should become contained database users for validation?
- Do you approve creating billable Azure resources, app registrations, and an API app client secret if deployment starts?

After the answers, show a checklist and ask for approval before implementation. Include phases for scaffold, Entra setup, database package, Azure infrastructure, post-provision, validation, and cleanup. Do not run `az`, `az ad`, `azd`, 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 and it supports Microsoft Entra/OBO validation; otherwise choose the lowest-cost SQL option that supports user-delegated authentication. 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 create app registrations and grant admin consent, `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 configure` OBO options: 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
- OBO concept: https://learn.microsoft.com/azure/data-api-builder/concept/security/authenticate-on-behalf-of
- User-delegated auth configuration: https://learn.microsoft.com/azure/data-api-builder/configuration/data-source#user-delegated-auth

Create this structure under the sample folder:

- `azure-infra/` for Bicep, `azure-up.ps1`, `azure-down.ps1`, `entra-setup.ps1`, `entra-teardown.ps1`, `resources.bicep`, and `post-provision.ps1`.
- `data-api/` for `dab-config.json` and a DAB Dockerfile that bakes the config into the image.
- `database/` for a SQL Database Project, seed data, and `Views/WhoAmI.sql`.
- `web-app/` for static HTML, CSS, and JavaScript with MSAL browser support.
- `aspire-apphost/` for build orchestration only.
- `mcp-inspector/` for MCP Inspector container assets and nginx same-origin proxy config.

Handle secrets first. Add `.env`, `**/bin`, and `**/obj` to `.gitignore` before writing secrets or local configuration. Store the API client secret only in local `.env` files for local preparation and in Azure Key Vault or Azure Container Apps secrets for Azure. Never inline secret values in Bicep, PowerShell scripts, generated JSON, logs, or reports. Generate secret references for Container Apps instead of plaintext environment values. Never print tokens, passwords, or client secret values. Redact all secret values as `***redacted***`.

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: any local web origin used for development and the deployed Azure Container Apps web FQDN. 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 for config shaping and validation where possible:

```dotnetcli
dab init --database-type mssql --connection-string "@env('DATABASE_CONNECTION_STRING')" --auth.provider EntraID --auth.audience "@env('ENTRA_AUDIENCE')" --auth.issuer "@env('ENTRA_ISSUER')" --rest.enabled true --graphql.enabled true --mcp.enabled true
dab configure --data-source.user-delegated-auth.enabled true --data-source.user-delegated-auth.provider EntraId --data-source.user-delegated-auth.database-audience "https://database.windows.net"
dab add WhoAmI --source dbo.vw_WhoAmI --source.type view --source.key-fields "UserName" --permissions "authenticated:read" --mcp.dml-tools true
dab validate --config data-api/dab-config.json
```

Use a bare Azure SQL connection string so DAB can inject the per-user OBO access token. Do not include `User ID`, `Password`, or `Authentication`.

```text
Server=tcp:<server>.database.windows.net,1433;Database=<database>;Encrypt=True;TrustServerCertificate=False;
```

Use this DAB data-source shape for OBO:

```json
{
	"data-source": {
		"database-type": "mssql",
		"connection-string": "@env('DATABASE_CONNECTION_STRING')",
		"user-delegated-auth": {
			"enabled": true,
			"provider": "EntraId",
			"database-audience": "https://database.windows.net"
		}
	}
}
```

Create `database/Views/WhoAmI.sql` to prove SQL sees the signed-in user.

```sql
CREATE VIEW dbo.vw_WhoAmI AS
SELECT CAST(SUSER_NAME() AS nvarchar(256)) AS 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}` };
}
```

For Azure, bake `dab-config.json` into the DAB image. Do not rely on volume mounts in Azure Container Apps.

```dockerfile
FROM mcr.microsoft.com/azure-databases/data-api-builder:latest
COPY dab-config.json /App/dab-config.json
```

Before any Azure post-provision command, list the exact `az`, `az acr`, `az containerapp`, and `sqlpackage` commands you intend to run and wait for explicit user approval. Post-provision in this order: deploy dacpac, set the Azure SQL Microsoft Entra admin, create contained database users or groups for validation, grant access to demo objects and `WhoAmI`, replace placeholders, build and push the DAB image, then update Container Apps.

```powershell
dotnet build database/database.sqlproj -c Release
sqlpackage /Action:Publish /SourceFile:database/bin/Release/database.dacpac /TargetConnectionString:"$sqlConn" /p:BlockOnPossibleDataLoss=false
az acr build --registry $acrName --image dab-api:latest --file ./data-api/Dockerfile ./data-api/
az containerapp update --name $dabAppName --resource-group $resourceGroup --image "$acrName.azurecr.io/dab-api:latest"
```

Deploy MCP Inspector with a same-origin proxy pattern and set `MCP_SERVER_URL` to the DAB `/mcp` endpoint.

```nginx
location /mcp {
	proxy_pass http://127.0.0.1:6277;
	proxy_http_version 1.1;
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header Connection "upgrade";
	proxy_buffering off;
}
```

Deploy SQL Commander with env var `ConnectionStrings__db` and ensure the connection string includes `TrustServerCertificate=true`.

```text
ConnectionStrings__db=Server=<server>.database.windows.net;Database=<database>;User Id=<user>;Password=<password>;TrustServerCertificate=true
```

Validation must prove OBO, not only API authentication:

- A direct Azure SQL query confirms the database is reachable, the deployed objects exist, and required contained users or groups exist.
- 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.
- The web app signs in with Microsoft Entra ID.
- Signed-in REST, GraphQL, and MCP calls include bearer headers and reach DAB under the `authenticated` role.
- The `WhoAmI` entity returns the signed-in user's UPN from `SUSER_NAME()`.
- `WhoAmI` does not return the DAB managed identity, service principal, or Container App identity.
- Anonymous REST and GraphQL calls return `401`.
- The DAB Container App database connection string contains no SQL password, no `User ID`, and no `Authentication` keyword.
- The API client secret exists only as a secret reference or redacted local value.
- MCP Inspector connects to DAB MCP with streamable HTTP.
- SQL Commander can browse the deployed schema.
- Required contained users or groups exist in Azure SQL.

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.

Troubleshoot with these checks:

- OBO token exchange fails: verify the API app has Azure SQL Database delegated `user_impersonation` permission and admin consent.
- SQL login fails for a token-identified principal: add the signed-in user or group as a contained user in the database.
- DAB returns 401 for valid bearer tokens: verify audience and issuer values in `dab-config.json`.
- SQL sees the service identity instead of the user: verify `user-delegated-auth`, the API client secret, and the bare SQL connection string.

관련 콘텐츠

• 데이터 API 작성기 빠른 시작
• 빠른 시작: Data API 작성기에서 SQL 행 수준 보안 사용
• 대리 사용자 위임 인증 구성
• 사용자가 위임한 인증 구성 참조
• 빠른 시작: Data API Builder에 Microsoft Entra 공급자 추가
• 데이터 API 작성기에서 Microsoft Entra ID 인증
• Data API Builder 버전 2.0의 새로운 기능