Skip to content

Commit 83222b6

Browse files
authored
edits
1 parent 512fc50 commit 83222b6

File tree

1 file changed

+6
-3
lines changed
  • src/connections/sources/catalog/libraries/server/node

1 file changed

+6
-3
lines changed

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

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -637,16 +637,20 @@ const analytics = new Analytics({
637637
638638
## OAuth 2.0
639639
640+
> info ""
641+
> OAuth 2.0 is currently in private beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
642+
640643
Enable [OAuth 2.0](/docs/connections/oauth/) in your Segment workspace to guarantee authorized communication between your server environment and Segment's Tracking API. To support the non-interactive server environment, the OAuth workflow used is a signed client assertion JWT.
641644
642645
You will need a public and private key pair where:
643646
- The public key is uploaded to the Segment dashboard.
644647
- The private key is kept in your server environment to be used by this SDK.
648+
645649
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.
646650
647-
You'll 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.
651+
You'll 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.
648652
649-
Be sure to implement handling for Analytics SDK errors. Good logging will help distinguish any configuration issues.
653+
Be sure to implement handling for Analytics SDK errors. Good logging helps distinguish any configuration issues.
650654
651655
For more information, see the [Segment OAuth 2.0 documentation](/docs/connections/oauth/).
652656
@@ -670,7 +674,6 @@ const analytics = new Analytics({
670674
analytics.on('error', (err) => { console.error(err) })
671675
672676
analytics.track({ userId: 'foo', event: 'bar' })
673-
674677
```
675678
## Troubleshooting
676679

0 commit comments

Comments
 (0)