Skip to content

Commit a7547f3

Browse files
Merge pull request #299605 from lb4368/nits
Minor updates to Credential Rotation how-to
2 parents d9d1317 + 837285d commit a7547f3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/operator-nexus/howto-credential-rotation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,15 +78,15 @@ The unknown state of credentials to the platform impacts monitoring and the abil
7878
In order to restore the state of the credential, it must be reset to a value that the platform recognizes. There are two options for this situation:
7979

8080
1. Run a [BareMetalMachine replace](./howto-baremetal-functions.md) action providing the current active credentials. The replace action allows the machine to use provided credentials to reset credential rotation. This is the recommended option if significant changes are made to the machine.
81-
1. Reset the BMC credential back to the value prior to the manual change. If a key vault is configured for receiving rotated credential, then the proper value may be obtained using information from the `secretRotationStatus` data for the Bare Metal Machine resource. The rotation status for the BMC Credential indicates the secret key and version within the key vault for the appropriate value. Once the credential is reset back, credential rotation will proceed normally.
81+
1. Reset the BMC credential back to the value prior to the manual change. If a key vault is configured for receiving rotated credential, then the proper value may be obtained using information from the `secretRotationStatus` data for the Bare Metal Machine resource. The rotation status for the BMC Credential indicates the secret key and version within the key vault for the appropriate value. Once the credential is set to match the value expected by the credential rotation system, rotation will proceed normally.
8282

8383
Example `secretRotationStatus` for BMC credential. Use the `secretName` and `secretVersion` to find the proper value in the cluster key vault.
8484
```
8585
{
8686
{
8787
...
8888
"secretArchiveReference": {
89-
"secretName": "YYYYYYYYYYYYYYYYYYYYYY-storage-appliance-credential-manager-ZZZZZZZ",
89+
"secretName": "YYYYYYYYYYYYYYYYYYYYYY-idrac-credential-manager-ZZZZZZZ",
9090
"secretVersion": "XXXXXXXXXXXXXX"
9191
},
9292
"secretType": "BMC Credential"

0 commit comments

Comments
 (0)