The documentation you are viewing is for Dapr v1.1 which is an older version of Dapr. For up-to-date documentation, see the latest version.

Authenticate requests from Dapr using token authentication

Require every incoming API request from Dapr to include an authentication token

For some building blocks such as pub/sub, service invocation and input bindings, Dapr communicates with an app over HTTP or gRPC. To enable the application to authenticate requests that are arriving from the Dapr sidecar, you can configure Dapr to send an API token as a header (in HTTP requests) or metadata (in gRPC requests).


Dapr 使用 JWT 令牌进行 API 身份验证。

Note, while Dapr itself is actually not the JWT token issuer in this implementation, being explicit about the use of JWT standard enables federated implementations in the future (e.g. OAuth2).

为了配置 API 身份验证,需要先使用任意 JWT 令牌兼容工具(如 和 secret 来生成您的令牌。

注意,这个 secret 仅仅用来生成令牌,Dapr 不需要知道或存储它

Configure app API token authentication in Dapr

令牌认证配置在 Kubernetes 和 自托管 Dapr deployments 下稍有不同:


In self-hosting scenario, Dapr looks for the presence of APP_API_TOKEN environment variable. If that environment variable is set while daprd process launches, Dapr includes the token when calling an app:

export APP_API_TOKEN=<token>

To rotate the configured token, simply set the APP_API_TOKEN environment variable to the new value and restart the daprd process.


在 Kubernetes deployment 里,Dapr 借助 Kubernetes secrets store 保存 JWT 令牌。 Start by creating a new secret:

kubectl create secret generic app-api-token --from-literal=token=<token> 

Note, the above secret needs to be created in each namespace in which you want to enable app token authentication

To indicate to Dapr to use the token in the secret when sending requests to the app, add an annotation to your Deployment template spec:

annotations: "true" "app-api-token" # name of the Kubernetes secret

When deployed, the Dapr Sidecar Injector automatically creates a secret reference and injects the actual value into APP_API_TOKEN environment variable.



To rotate the configured token in self-hosted, simply set the APP_API_TOKEN environment variable to the new value and restart the daprd process.


如果需要更新在 Kubernates 中已配置的令牌,更新先前在每个命名空间中创建的 secret 的令牌。 您可以使用 kubectl patch 命令执行此操作,但更简单的方法是,使用 manifest 更新每个命名空间中的这些对象:

apiVersion: v1
kind: Secret
  name: app-api-token
type: Opaque
  token: <your-new-token>

然后将其 apply 到每个命名空间:

kubectl apply --file token-secret.yaml --namespace <namespace-name>

为了让 Dapr 开始使用新令牌,需要对你的每个 deployment 进行滚动升级:

kubectl rollout restart deployment/<deployment-name> --namespace <namespace-name>

请注意,假设您的服务配置为多个副本,则 key 滚动过程不会导致任何停机。

Authenticating requests from Dapr

Once app token authentication is configured in Dapr, all requests coming from Dapr include the token:


In case of HTTP, inspect the incoming request for presence of dapr-api-token parameter in HTTP header:

dapr-api-token: <token>


When using gRPC protocol, inspect the incoming calls for the API token on the gRPC metadata:




In Kubernetes, it’s recommended to mount the secret to your pod as an environment variable. Assuming we created a secret with the name app-api-token to hold the token:

  - name: mycontainer
    image: myregistry/myapp
    - secretRef:
      name: app-api-token


在自托管模式下,您可以将令牌设置为应用程序的环境变量 :

export APP_API_TOKEN=<my-app-token>


Last modified January 1, 0001