dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

clarify the header/metadata coming from Dapr 

Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
This commit is contained in:
Hannah Hunter 2024-02-28 10:42:24 -05:00
parent 5cd8da4417
commit b6807949a6
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
daprdocs/content/en/operations/security/app-api-token.md
View File

@ -89,14 +89,14 @@ kubectl rollout restart deployment/<deployment-name> --namespace <namespace-name
## Authenticating requests from Dapr ## Authenticating requests from Dapr
Once app token authentication is configured in Dapr, all requests *coming from Dapr* include the token. Once app token authentication is configured using the environment variable or Kubernetes secret `app-api-token`, the Dapr sidecar always includes the HTTP header/gRPC metadata `dapr-api-token: <token>` in the calls to the app. From the app side, ensure you are authenticating using the `dapr-api-token` value, even though you set `app-api-token` to enable API authentication.
### HTTP ### HTTP
In case of HTTP, in your code look for the HTTP header `dapr-api-token` in incoming requests: In your code, look for the HTTP header `dapr-api-token` in incoming requests:
```text ```text
dapr-api-token: <token> a-api-token: <token>
``` ```
### gRPC ### gRPC