Skip to content

Commit a358696

Browse files
committed
Apply suggestions from code review
1 parent a34f4ca commit a358696

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

src/connections/sources/catalog/libraries/server/node/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -635,9 +635,9 @@ const analytics = new Analytics({
635635
})
636636
```
637637
638-
### OAuth 2
638+
### OAuth 2.0
639639
640-
In order to guarantee authorized communication between your server environment and Segment's Tracking API, you can enable OAuth 2 in your Segment workspace. To support the non-interactive server environment, the OAuth workflow used is a signed client assertion JWT. You will need a public and private key pair where the public key is uploaded to the segment dashboard and the private key is kept in your server environment to be used by this SDK. Your server will verify its identity by signing a token request and will receive a token that is used to to authorize all communication with the Segment Tracking API.
640+
In order to guarantee authorized communication between your server environment and Segment's Tracking API, you can enable [OAuth 2.0](/docs/connections/oauth/) in your Segment workspace. To support the non-interactive server environment, the OAuth workflow used is a signed client assertion JWT. You will need a public and private key pair where the public key is uploaded to the segment dashboard and the private key is kept in your server environment to be used by this SDK. Your server will verify its identity by signing a token request and will receive a token that is used to to authorize all communication with the Segment Tracking API.
641641
642642
You will also need to provide the OAuth Application ID and the public key's ID, both of which are provided in the Segment dashboard. There are also options available to specify the authorization server, custom scope, maximum number of retries, or a custom HTTP client if your environment has special rules for separate segment endpoints.
643643

src/connections/sources/catalog/libraries/server/python/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -560,9 +560,9 @@ analytics.track('9742', 'Song Played', context={
560560

561561
Be sure to see the full [reference of supported keys](/docs/connections/spec/common/#context).
562562

563-
### OAuth 2
563+
### OAuth 2.0
564564

565-
In order to guarantee authorized communication between your server environment and Segment's Tracking API, you can enable OAuth 2 in your Segment workspace. To support the non-interactive server environment, the OAuth workflow used is a signed client assertion JWT. You will need a public and private key pair where the public key is uploaded to the segment dashboard and the private key is kept in your server environment to be used by this SDK. Your server will verify its identity by signing a token request and will receive a token that is used to to authorize all communication with the Segment Tracking API.
565+
In order to guarantee authorized communication between your server environment and Segment's Tracking API, you can enable [OAuth 2.0](/docs/connections/oauth/) in your Segment workspace. To support the non-interactive server environment, the OAuth workflow used is a signed client assertion JWT. You will need a public and private key pair where the public key is uploaded to the segment dashboard and the private key is kept in your server environment to be used by this SDK. Your server will verify its identity by signing a token request and will receive a token that is used to to authorize all communication with the Segment Tracking API.
566566

567567
You will also need to provide the OAuth Application ID and the public key's ID, both of which are provided in the Segment dashboard. There are also options available to specify the authorization server, custom scope, maximum number of retries, or a custom HTTP client if your environment has special rules for separate segment endpoints.
568568

0 commit comments

Comments
 (0)