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: articles/operator-nexus/how-to-credential-manager-key-vault.md
+25-58Lines changed: 25 additions & 58 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,96 +113,63 @@ Refer to [_Grant Managed Identity Access to a Key Vault for Credential Rotation_
113
113
## Configure Key Vault Using Managed Identity for Cluster
114
114
115
115
> [!IMPORTANT]
116
-
> Please note that this method for configuring a key vault for credential rotation is in preview. **This method can only be used with key vault that do not have firewall enabled.** If your environment requires the key vault firewall be enabled, use the existing [Cluster Manager]() identity method.
116
+
> Please note that this method for configuring a key vault for credential rotation is in preview. **This method can only be used with key vaults that do not have firewall enabled.** If your environment requires the key vault firewall be enabled, use the existing [Cluster Manager]() identity method.
117
117
118
-
Beginning with the 2024-10-01-preview API, managed identities in the Nexus Cluster resource can be used instead of Cluster Manager. The Cluster identity may be system-assigned or [user-assigned](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities), and can be managed directly via APIs or via CLI.
118
+
Beginning with the 2024-10-01-preview API, managed identities in the Nexus Cluster resource can be used instead of Cluster Manager. The Cluster managed identity may be system-assigned or [user-assigned](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities), and can be managed directly via APIs or via CLI.
119
119
120
120
> [!NOTE]
121
121
> If Nexus Cluster managed identity is configured for the key vault, then these settings will supersede settings configured in [_Configure Key Vault Using Managed Identity for Cluster Manager_](#configure-key-vault-using-managed-identity-for-cluster-manager)
122
122
123
-
These examples describe how to configure a managed identity for a Nexus Cluster.
The Nexus Cluster _secret-archive-settings_ specify the Azure Key Vault URI where rotated credentials will be stored and the managed identity which will be used to access it.
126
+
127
+
These examples describe how to configure a managed identity for a Nexus Cluster and configure it as part of _secret-archive-settings_.
128
+
129
+
> [!NOTE]
130
+
> Secret archive settings specify the Key Vault URI, not the Key Vault resource ID, and the managed identity specfied must be configured for the Nexus Cluster.
124
131
125
-
- Create Nexus Cluster with system-assigned identity
132
+
- Create Nexus Cluster with system-assigned identity to access Key Vault for rotated credentials.
126
133
```azurecli-interactive
127
134
az networkcloud cluster create --name "<cluster-name>" \
Register the Key Vault URI and managed identity to be used in the secret archive settings for the Nexus cluster.
158
-
159
-
> [!NOTE]
160
-
> Secret archive settings specify the Key Vault URI, not the Key Vault resource ID, and the managed identity specfied must be configured for the Nexus Cluster.
161
-
162
-
Example:
168
+
For more help:
163
169
164
-
- Using a system-assigned identity:
165
-
166
-
```azurecli
167
-
az rest --method PATCH --url ${CLUSTER_ID}?api-version=2024-10-01-preview --body @./sami-body.json
0 commit comments