# Dapr v1.15.13

2025-10-30 · [릴리스 노트 원문](https://github.com/dapr/dapr/releases/tag/v1.15.13) · [전체 정리](https://ratatosk.io/ko/releases/dapr/v1.15.13)

중요 수정 2 · 기타 1

## 중요 수정 (2)

### gRPC 콜백 앱 토큰 전달 수정

- 영향 대상: `APP_API_TOKEN`이 설정된 gRPC PubSub 구독, 바인딩 또는 잡

이전에는 해당 콜백이 gRPC 메타데이터에 토큰을 포함하지 않아 애플리케이션이 Dapr에서 보낸 요청을 인증할 수 없었습니다. 이제 발신 메타데이터의 `dapr-api-token` 헤더에 토큰을 포함합니다.

> ## APP_API_TOKEN not passed in gRPC metadata for app callbacks
> ### Problem
> When `APP_API_TOKEN` was configured, the token was not being passed in gRPC metadata for app callbacks including:
> - PubSub subscriptions
> - Bindings
> - Jobs
> This meant that applications using gRPC protocol could not authenticate incoming requests from Dapr when using the app API token security feature.
> ### Impact
> Applications that configured `APP_API_TOKEN` to secure their endpoints could not validate that incoming gRPC requests were from their Dapr sidecar. This broke the app API token authentication feature for gRPC applications.
> ### Root Cause
> The gRPC subscription delivery, binding, and job callback code paths were directly calling the app's gRPC client without going through the channel layer abstraction. The channel layer is responsible for injecting the `APP_API_TOKEN` in the `dapr-api-token` metadata header, but these direct calls bypassed this mechanism.
> ### Solution
> Centralized the `APP_API_TOKEN` injection logic in a helper function (`AddAppTokenToContext`) in the gRPC channel layer. Updated all gRPC app callback code paths (pubsub subscriptions, bindings, and job callbacks) to use this helper, ensuring the token is consistently added to the outgoing gRPC context metadata. Added comprehensive integration tests to verify token passing for all callback scenarios in both HTTP and gRPC protocols.

### Pulsar PubSub OAuth 토큰 갱신 수정

- 영향 대상: 만료되는 OAuth 토큰을 사용하는 Pulsar PubSub (추정)

OAuth 토큰이 만료되었을 때 컴포넌트가 토큰을 갱신하지 않아 애플리케이션에서 메시지를 수신하거나 게시할 수 없었습니다. 이제 토큰이 만료되면 갱신하므로 해당 상황에서도 애플리케이션이 메시지를 수신하고 게시할 수 있습니다.

> The pulsar pubsub component was not renewing the OAuth token when it expired.
> ### Impact
> Applications using the pulsar pubsub component could not receive/publish messages when the OAuth token expired.
> ### Root Cause
> There was a bug in the component code that was preventing the OAuth token from being renewed when it expired.
> ### Solution
> Fixed the bug in the component code ensuring the OAuth token is renewed when it expires. Also added a test to verify the token renewal functionality. Fixed in https://github.com/dapr/components-contrib/pull/4079

## 기타 (1)

- OAuth 토큰 갱신 테스트 추가

---

정리 내용은 AI가 작성하므로 틀릴 수 있으며, 보증 없이 제공합니다.
