Skip to content

CXP-2212: document C1 redirect URI and integration key classification #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
luisina-santos merged 3 commits into from
Aug 28, 2026
Merged

CXP-2212: document C1 redirect URI and integration key classification #70

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bf63882
docs: document C1 redirect URI and integration key classification
luisina-santos Aug 27, 2026
f544efc
docs: fix inaccurate claim about self-hosted redirect URI
luisina-santos Aug 28, 2026
8e68a99
docs: soften integration key classification guidance
luisina-santos Aug 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/connector.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,12 +60,16 @@ A user with access to the **Docusign Admin console** must perform this task.
</Step>
<Step>
On the app configuration screen, carefully copy and save the **Client ID** (also called an integration key).

You'll be asked to classify the integration key. This choice affects production billing and [can't be changed later](https://developers.docusign.com/platform/go-live/#ik-classifications). The key is created and used against your own DocuSign account in both hosting modes, so **Private custom integration** — DocuSign's description is *"used internally by your employees or your customers' employees"* — matches most setups. If you're going through C1's **Custom App (Demo Environment)** field group, you may instead consider **Third-party integration key** — *"using a partner integration that requires your own integration key"* — since C1 is the party invoking it on your behalf; confirm with DocuSign which classification fits your situation before proceeding, since it isn't reversible.
</Step>
<Step>
Click **Add Secret Key**, then carefully copy and save the client secret.
</Step>
<Step>
In the **Redirect URI** field, enter any URI of your choice (such as http://example.com/callback) and click **Add**.
In the **Redirect URI** field:
- If you're configuring a **self-hosted** connector, enter any URI of your choice (such as http://example.com/callback) and click **Add**. Nothing needs to be listening at that address — the `--configure` flow prints an authorization URL, and after you authorize, DocuSign redirects your browser there; copy the `code` parameter from the resulting (unreachable) URL and paste it when prompted. Whatever value you register here must also be passed as `--redirect-uri` / `BATON_REDIRECT_URI`, or the authorization and token exchange will fail.
- If you're configuring a **Cloud-hosted (demo environment)** connector, enter `https://accounts.conductor.one/oauth/callback` and click **Add**. C1 completes the OAuth flow through this URL; DocuSign rejects the authorization request if it isn't registered here.

@github-actions github-actions Bot Aug 28, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Suggestion: https://accounts.conductor.one/oauth/callback appears nowhere else in this repo (redirect-uri is ExportTargetCLIOnly in pkg/config/config.go:32-37, so the cloud-hosted path never passes it through the connector), which means this exact string can't be verified here. If it doesn't match the redirect URI C1's platform actually sends, DocuSign rejects the authorization and setup fails at the last step. Worth confirming the literal value with the platform team (and whether it varies by environment/region) before merging. (Medium confidence.)

</Step>
<Step>
Under **Authentication**, enable **Authorization Code Grant**.
Expand Down
Loading