You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: daprdocs/content/en/operations/configuration/secret-scope.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,6 @@ title: "How-To: Limit the secrets that can be read from secret stores"
4
4
linkTitle: "Limit secret store access"
5
5
weight: 3000
6
6
description: "Define secret scopes by augmenting the existing configuration resource with restrictive permissions."
7
-
description: "Define secret scopes by augmenting the existing configuration resource with restrictive permissions."
8
7
---
9
8
10
9
In addition to [scoping which applications can access a given component]({{% ref "component-scopes.md"%}}), you can also scope a named secret store component to one or more secrets for an application. By defining `allowedSecrets` and/or `deniedSecrets` lists, you restrict applications to access only specific secrets.
data-modal-disclaimer="Answers are based on the Dapr docs, relevant websites, and GitHub repositories. Always double check the results and please provide feedback with a 👍 or 👎 so we continue to improve this service."
14
-
data-modal-example-questions="How do I get started with Dapr?, How do I use Kafka with Dapr Pub/Sub?, How do I run Dapr in production?, How do I build agentic AI with Dapr?"
15
-
data-modal-example-questions-title="Try asking:"
16
-
data-modal-ask-ai-input-placeholder="Ask me anything Dapr-related..."
0 commit comments