Skip to content

Add auth setup, validation, and troubleshooting for Linear, Salesforce, and Datadog#329

Open
c1-dev-bot[bot] wants to merge 1 commit into
mainfrom
docs/agnt-578-auth-setup-docs
Open

Add auth setup, validation, and troubleshooting for Linear, Salesforce, and Datadog#329
c1-dev-bot[bot] wants to merge 1 commit into
mainfrom
docs/agnt-578-auth-setup-docs

Conversation

@c1-dev-bot

@c1-dev-bot c1-dev-bot Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds detailed authentication setup documentation for three representative Tier 1 vendors, establishing the auth docs pattern with validation and troubleshooting sections.

Linear (API key baseline)

  • Added prerequisites documenting Admin/Owner role requirement for API key creation
  • Added warning that API keys inherit the creator's permissions
  • Added credential validation steps using a curl command against the Linear GraphQL API
  • Added troubleshooting section for auth failures and provisioning permission issues

Salesforce (OAuth/JWT/Client Credentials complexity)

  • Added auth method comparison table helping operators choose between JWT Bearer, Client Credentials, OAuth, and username/password (deprecated)
  • Added recommendation for JWT Bearer or Client Credentials for production
  • Added credential validation steps for JWT Bearer and Client Credentials methods with expected responses and error troubleshooting

Datadog (API key + app key)

  • Added site identification table mapping all Datadog regional URLs to their site configuration values
  • Documented required application key scopes (Access Management, Teams) with explanation of scope inheritance
  • Added credential validation using the /api/v1/validate endpoint with expected response format
  • Added troubleshooting for invalid API keys and missing application key scopes

Remaining unknowns / blockers

  • Gmail/Google Drive (Google DWD/JWT): Not included in this batch — requires investigation of baton-google connector for domain-wide delegation setup, which involves Google Workspace admin console configuration and service account impersonation
  • Gong (Basic/bearer/OAuth ambiguity): Not included — needs investigation of which auth methods the baton-gong connector actually supports and how ambiguity between methods is resolved

Automated PR Notice

This PR was automatically created by c1-dev-bot as a potential documentation update.

This documentation requires:

  • Human review for accuracy and completeness
  • Verification that it matches current product behavior
  • Approval from the appropriate team before merging

…sforce, and Datadog

Enhance connector documentation with detailed authentication setup guidance:

- Linear: Add prerequisites (Admin/Owner role requirement), API key validation
  steps using curl, and troubleshooting for auth failures and provisioning
  permission issues.

- Salesforce: Add auth method comparison table to help operators choose between
  JWT Bearer, Client Credentials, OAuth, and username/password. Add credential
  validation steps for JWT Bearer and Client Credentials methods.

- Datadog: Add site identification table mapping Datadog URLs to site values,
  document required application key scopes (Access Management, Teams), add
  credential validation using the /api/v1/validate endpoint, and add
  troubleshooting for invalid keys and missing scopes.
@linear-code

linear-code Bot commented Jun 9, 2026

Copy link
Copy Markdown

AGNT-578

@mintlify

mintlify Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
conductorone 🟢 Ready View Preview Jun 9, 2026, 12:42 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants