Skip to content

Commit 5c441ff

Browse files
ugh this indentation is hard
1 parent 83e6fc1 commit 5c441ff

File tree

1 file changed

+3
-9
lines changed

1 file changed

+3
-9
lines changed

src/pages/guides/authentication/ServerToServerAuthentication/implementation.md

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -79,24 +79,18 @@ You can rotate secrets for your credential through the Dev Console UI and [progr
7979
To rotate client secrets through the UI, follow the steps below on the credential overview screen -
8080

8181
1. Add a new client secret to your credential .
82-
8382
![](../../../images/oauth-server-to-server-credential-add-client-secret.png)
84-
8583
![](../../../images/oauth-server-to-server-credential-added-client-secret.png)
8684

8785
2. Update your application to replace your old client secret with the new one you added.
88-
3. Check the client secret last used timestamp to make sure your application is no longer using the old client secret.
8986

87+
3. Check the client secret last used timestamp to make sure your application is no longer using the old client secret.
9088
![](../../../images/oauth-server-to-server-credential-check-client-secret-timestamps.png)
9189

9290
4. Once sure that you have successfully replaced the client secret, you can delete the old client secret.
93-
9491
![](../../../images/oauth-server-to-server-credential-delete-old-client-secret.png)
95-
96-
97-
<InlineAlert slots="text"/>
98-
99-
Once a client secret is deleted, you cannot restore it. So be extra sure you have replaced the old client secret with the new one in all locations.
92+
<InlineAlert slots="text"/>
93+
Once a client secret is deleted, you cannot restore it. So be extra sure you have replaced the old client secret with the new one in all locations.
10094

10195

10296
### Rotating client secrets programmatically

0 commit comments

Comments
 (0)