This page contains the setup guide and reference information for the Adobe Sign connector.
Prerequisites
Before connecting your Adobe Sign account, ensure that:
-
You have an active Adobe Sign account.
-
You have access to the Admin Console and permission to manage API Applications.
Setup Guide
Follow these steps to connect your Adobe Sign account to Keragon:
-
Visit secure.adobesign.com and sign in to your account.
-
Navigate to the Account section.
-
Click on Acrobat Sign API.
-
Select API Applications.
-
Click Create a new application.
-
Fill in the Name and Display Name.
-
For Application Type, select PARTNER.
-
Click Save to create the application.
-
After creation, select your new application from the list.
-
Click Configure OAuth for Application.
-
In the Redirect URI field, enter the following URLs:
-
Choose the required OAuth scopes based on your integration needs.
-
Click Save.
-
Return to the application list and select your application again.
-
Click View / Edit to open the details.
-
Copy the Client ID and Client Secret.
-
Go to app.keragon.com and open the Adobe Sign connector setup.
-
Paste the Client ID and Client Secret into the respective fields.
-
Click Connect to authorize Keragon via OAuth.
Need more help connecting?
Check the fully extended Adobe Sign connector setup guide for screenshots, detailed steps, and additional context.
Note: Be sure to use the correct redirect URIs and select all required scopes to avoid connection issues.
Troubleshooting and Common Errors
Error Message | Cause | Suggested Fix |
---|---|---|
invalid_client |
Incorrect Client ID or Secret | Double-check both values and ensure they're from the same registered app. |
redirect_uri_mismatch |
Redirect URI not registered | Ensure both Keragon callback URIs are correctly added in the Adobe Sign application. |
insufficient_scope |
Missing required OAuth scopes | Reconfigure the application with all needed scopes. |
401 Unauthorized |
Token expired or revoked | Reauthenticate in Keragon by clicking Connect again. |
Limitations and Notes
-
Authentication uses OAuth 2.0 via Client ID and Secret.
-
Make sure both Keragon redirect URIs are added exactly to avoid redirect mismatches.
-
Scopes must be manually selected during app setup—permissions depend on your workflow needs.