Create third-party OAuth provider records
- UpdatedAug 3, 2023
- 5 minutes to read
- Vancouver
- Building applications
The Vancouver release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.
Create third-party OAuth provider records to enable each of your instances to access the API endpoints you've created.
Before you begin
Complete the tasks in Create OAuth API endpoints for external clients.
In the top right corner of your instance, make sure you set the application scope to Global.
Open all of your instances (development, test, production, and the like) in separate browser tabs. Begin the steps below on the production instance.
Role required: admin
Procedure
-
On your production instance, navigate to All > System OAuth > Application Registry.
You must create three records here, one for each of the three instances (development, test, and production). If you have any additional non-production instances (staging, and the like), create a record for each of those following the method shown here.
- Select New.
- Select Connect to a third party OAuth Provider to create a record for your development instance.
-
On the form, fill in the fields.
Table 1. Application Registries form Field Action Name Enter Dev Instance Connection. Client ID - On your development instance, open the Application Registry list (All > System OAuth > Application Registry).
- Open the Pipeline Development Client record.
- Copy the Client ID.
- On your production instance, paste the Client ID from your development instance into the Client ID field.
Client Secret - On your development instance, open the Application Registry list (All > System OAuth > Application Registry).
- Open the Pipeline Development Client record.
- Unlock the Client Secret field and copy the text.
- On your production instance, paste the Client Secret from your development instance in the Client Secret field.
Default Grant type Change to Authorization code. Authorization URL - Unlock the field.
- Enter the URL for your development instance followed by oauth_auth.do.
- Lock the field.
Token URL - Unlock the field.
- Enter the URL for your development instance followed by oauth_token.do.
- Lock the field.
- Select Submit.
- Select New.
- Select Connect to a third party OAuth Provider to create a record for your test instance.
-
On the form, fill in the fields.
Table 2. Application Registries form Field Action Name Enter Test Instance Connection. Client ID - On your test instance, open the Application Registry list (All > System OAuth > Application Registry).
- Open the Pipeline Test Client record.
- Copy the Client ID.
- On your production instance, paste the Client ID from your test instance into the Client ID field.
Client Secret - On your test instance, open the Application Registry list (All > System OAuth > Application Registry).
- Open the Pipeline Test Client record.
- Unlock the Client Secret field and copy the text.
- On your production instance, paste the Client Secret from your test instance in the Client Secret field.
Default Grant type Change to Authorization code. Authorization URL - Unlock the field.
- Enter the URL for your test instance followed by oauth_auth.do.
- Lock the field.
Token URL - Unlock the field.
- Enter the URL for your test instance followed by oauth_token.do.
- Lock the field.
- Select Submit.
- On the Application Registry list, select the Pipeline Controller Client record.
- Copy the Client ID and paste it somewhere like a notes application.
- Unlock the Client Secret field, copy the text, and paste it in a note with the Client ID.
- Go back to the Application Registry list and select New.
- Select Connect to a third party OAuth Provider to create a record for your production instance.
-
On the form, fill in the fields.
Table 3. Application Registries form Field Action Name Enter Prod Instance Connection. Client ID - Copy the Client ID that you noted down.
- Paste the Client ID into the Client ID field.
Client Secret - Copy the Client Secret that you noted down.
- Unlock the Client Secret field, and paste the text in the field.
Default Grant type Change to Authorization code. Authorization URL - Unlock the field.
- Enter the URL for your production instance followed by oauth_auth.do.
- Lock the field.
Token URL - Unlock the field.
- Enter the URL for your production instance followed by oauth_token.do.
- Lock the field.
-
Select Submit.
Important: Complete the next steps on your development instance.
-
On your development instance, navigate to All > System OAuth > Application Registry.
- Select New.
- Select Connect to a third party OAuth Provider to create a record for your production instance.
-
On the form, fill in the fields.
Table 4. Application Registries form Field Action Name Enter Prod Instance Connection. Client ID - Copy the Client ID that you noted down.
- Paste the Client ID into the Client ID field.
Client Secret - Copy the Client Secret that you noted down.
- Unlock the Client Secret field, and paste the text in the field.
Default Grant type Change to Authorization code. Authorization URL - Unlock the field.
- Enter the URL for your production instance followed by oauth_auth.do.
- Lock the field.
Token URL - Unlock the field.
- Enter the URL for your production instance followed by oauth_token.do.
- Lock the field.
-
Select Submit.
Important: Complete the next steps on your test instance.
- On your test instance, navigate to All > System OAuth > Application Registry.
- Select New.
- Select Connect to a third party OAuth Provider to create a record for your production instance.
-
On the form, fill in the fields.
Table 5. Application Registries form Field Action Name Enter Prod Instance Connection. Client ID - Copy the Client ID that you noted down.
- Paste the Client ID into the Client ID field.
Client Secret - Copy the Client Secret that you noted down.
- Unlock the Client Secret field, and paste the text in the field.
Default Grant type Change to Authorization code. Authorization URL - Unlock the field.
- Enter the URL for your production instance followed by oauth_auth.do
- Lock the field.
Token URL - Unlock the field.
- Enter the URL for your production instance followed by oauth_token.do
- Lock the field.
- Select Submit.
- (Optional) Repeat steps 22–26 for any other non-production instances that you have (staging, and the like).
What to do next
Now that you’ve completed the pre-work for using OAuth, complete all the steps in Use OAuth to create pipeline credentials on the specified instances.