Skip to content

Commit cbdfb8b

Browse files
committed
Update SP expectations
1 parent 29615dc commit cbdfb8b

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/operator-nexus/howto-service-principal-rotation.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ author: sbatchu0108
99
ms.author: sbatchu
1010
---
1111

12-
# Service principal rotation on the target cluster
12+
# Service Principal rotation on the target Cluster
1313

1414
This document provides an overview on the process of performing Service Principal rotation on the target Nexus cluster.
1515
In alignment with security best practices, a Security Principal should be rotated periodically. Anytime the integrity of the Service Principal is suspected or known to be compromised, it should be rotated immediately.
@@ -24,38 +24,38 @@ In alignment with security best practices, a Security Principal should be rotate
2424
6. Service Principal rotation should be performed prior to the configured credentials expiring.
2525
7. Service Principal should have owner privilege on the subscription of the target cluster.
2626

27-
## Append secondary credential to the existing service principal
27+
## Append secondary credential to the existing Service Principal
2828

29-
List existing credentials info for the service principal
29+
List existing credentials info for the Service Principal
3030

3131
```azurecli
3232
az ad app credential list --id "<SP Application (client) ID>"
3333
```
3434

35-
Append secondary credential to the service principal. Please copy the resulting generated password somewhere safe.
35+
Append secondary credential to the Service Principal. Please copy the resulting generated password somewhere safe, following best practices.
3636

3737
```azurecli
3838
az ad app credential reset --id "<SP Application (client) ID>" --append --display-name "<human-readable description>"
3939
```
40-
## Create a new service principal
40+
## Create a new Service Principal
4141

42-
New service principal should have owner privilege scope on the target cluster subscription.
42+
New Service Principal should have owner privilege scope on the target Cluster subscription.
4343

4444
```azurecli
4545
az ad sp create-for-rbac -n "<service principal display name>" --role owner --scopes /subscriptions/<subscription-id>
4646
```
4747

48-
## Rotate service principal on the target cluster
48+
## Rotate Service Principal on the target Cluster
4949

50-
Service principal can be rotated on the target cluster by supplying the new information, which can either be only secondary credential update or it could be the new service principal for the target cluster.
50+
Service Principal can be rotated on the target Cluster by supplying the new information, which can either be only secondary credential update or it could be the new Service Principal for the target Cluster.
5151

5252
```azurecli
5353
az networkcloud cluster update --resource-group "<resourceGroupName>" --cluster-service-principal application-id="<sp app id>" password="<cleartext password>" principal-id="<sp id>" tenant-id="<tenant id>" -n <cluster name> --subscription <subscription-id>
5454
```
5555

56-
## Verify new service principal update on the target cluster
56+
## Verify new Service Principal update on the target Cluster
5757

58-
Cluster show will list the new service principal changes if its rotated on the target cluster.
58+
Cluster show will list the new Service Principal changes if its rotated on the target Cluster.
5959

6060
```azurecli
6161
az networkcloud cluster show --name "clusterName" --resource-group "resourceGroup"
@@ -72,9 +72,9 @@ In the output, you can find the details under `clusterServicePrincipal` property
7272
```
7373

7474
> [!NOTE]
75-
> Ensure you're using the correct service principal ID(object ID in Azure) when updating it. There are two different object IDs retrievable from Azure for the same Service Principal name, follow these steps to find the right one:
75+
> Ensure you're using the correct Service Principal ID(object ID in Azure) when updating it. There are two different object IDs retrievable from Azure for the same Service Principal name, follow these steps to find the right one:
7676
> 1. Avoid retrieving the object ID from the Service Principal of type application that appears when you search for service principal on the Azure portal search bar.
7777
> 2. Instead, Search for the service principal name under "Enterprise applications" in Azure Services to find the correct object ID and use it as principal ID.
7878
7979
If you still have questions, [contact support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
80-
For more information about Support plans, see [Azure Support plans](https://azure.microsoft.com/support/plans/response/).
80+
For more information about Support plans, see [Azure Support plans](https://azure.microsoft.com/support/plans/response/).

0 commit comments

Comments
 (0)