Skip to content

Commit 73f882d

Browse files
stayseesongrchinn1
andauthoredOct 2, 2023
Apply suggestions from code review
Co-authored-by: rchinn-segment <[email protected]>
1 parent 0cf6d22 commit 73f882d

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed
 

‎src/api/public-api/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Learn more about [GitHub's secret scanning program](https://docs.github.com/en/d
4646
4747
You can authenticate and authorize the Public API using [OAuth 2.0](/docs/connections/oauth).
4848

49-
### Frequently Asked Questions
49+
### Frequently asked questions
5050
#### What should I do if I see a notification that my token was exposed?
5151
In most cases, identifying and revoking an exposed token takes seconds. Segment recommends you check the [audit trail](/docs/segment-app/iam/audit-trail/) to ensure no unauthorized actions were taken with the token.
5252

‎src/connections/oauth.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ hidden: true
66
OAuth 2.0 is an online authorization standard that uses tokens to grant access to API resources like Segment’s tracking API. You can use OAuth 2.0 as a security requirement for connections to third-party tools.
77

88
> info ""
9-
> This feature is currently in pilot and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. OAuth 2.0 only supports server to Segment communication, a machine-to-machine workflow. Take a look at the [supported sources](#supported-sources) to see what sources are currently supported.
9+
> This feature is currently in pilot and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. OAuth 2.0 only supports server to Segment communication, a machine-to-machine workflow. Take a look at the [supported sources](#supported-sources) to see what sources Segment supports.
1010
1111
## Permissions
1212
Depending on your workspace permissions, your access to OAuth apps is limited.
@@ -23,11 +23,11 @@ Function Read-only | You can only view OAuth apps.
2323
## Create an OAuth app
2424

2525
> info ""
26-
> You must have already created workspace in Segment to use OAuth.
26+
> You must have already created a workspace in Segment to use OAuth.
2727
2828
To create a new OAuth application:
2929

30-
1. Navigate to **Settings > Workspace** settings and select the Access Management tab.
30+
1. Navigate to **Settings > Workspace settings** and select the Access Management tab.
3131
2. Select the **OAuth application** tab within the **Access Management** page.
3232
3. Click **Create OAuth app**.
3333
4. Enter the configuration settings:
@@ -38,7 +38,7 @@ To create a new OAuth application:
3838
Public key | Upload a public key in PEM format to authenticate through the OAuth application. You can upload a second public key after you create the OAuth application. You can create a public key by running the script: `openssl rsa -in private.pem -pubout -outform PEM -out public.pem`
3939
Public key name | Enter a name for your public key.
4040
Token expiration period | You can choose between: 1 day, 2 days, 3 days, 1 week, 2 weeks, 3 weeks, 30 days.
41-
Scope | This specifies what type of access is needed for each API. See the list of [supported scopes](#supported-scopes).
41+
Scope | This specifies what type of access you need for each API. See the list of [supported scopes](#supported-scopes).
4242
5. Click **Create**.
4343

4444
Once you create your OAuth app, you can now connect a source to your OAuth app.
@@ -79,7 +79,7 @@ To request the access token, run:
7979
## Edit an OAuth application
8080
To edit an existing OAuth application:
8181

82-
1. Navigate to **Settings > Workspace** settings and select the **Access Management** tab.
82+
1. Navigate to **Settings > Workspace settings** and select the **Access Management** tab.
8383
2. Select the **OAuth application** tab within the **Access Management** page.
8484
3. Click the application name of the OAuth application you want to edit.
8585
4. On the **Overview** tab you can:
@@ -97,7 +97,7 @@ To edit an existing OAuth application:
9797

9898
## Delete an OAuth app
9999
> info ""
100-
> In order to delete an OAuth app, you must remove all connected sources from the app.
100+
> To delete an OAuth app, you must remove all connected sources from the app.
101101
102102
To delete an OAuth app:
103103
1. Navigate to **Settings > Workspace settings** and select the **Access Management** tab.

0 commit comments

Comments
 (0)
Please sign in to comment.