Skip to content

Commit 53735a8

Browse files
authored
Fix : Table issues
1 parent 7851ec5 commit 53735a8

File tree

1 file changed

+1
-1
lines changed
  • src/pages/guides/authentication/ServerToServerAuthentication

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Unlike the Service Account (JWT) credential, the new credential does not use a p
3333
Lastly, while the new OAuth Server-to-Server credentials do not use expiring certificates, they still allow client secret rotation through the UI and API. Read more about [rotating secrets programmatically](./implementation.md#rotating-client-secrets-programmatically) in our guide on [rotating client secrets](./implementation.md#rotating-client-secrets).
3434

3535

36-
| | OAuth Server-to-Server credential | Service Account (JWT) credential | | |
36+
| | OAuth Server-to-Server credential | Service Account (JWT) credential |
3737
|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
3838
| Do expiring certificates need to be replaced every year? | This credential does not use public certificates or private key pairs. You are not forced to rotate certificates every year. | You need to rotate the public certificate and private key pair every year. |
3939
| Generating access tokens for experimentation | You can generate an access token for quick experimentation with a [one-click button](./implementation.md#generate-access-tokens) on the Developer Console. | Generating access tokens is a 3-step process spanning the Developer Console UI and your command-line terminal. |

0 commit comments

Comments
 (0)