Adobe Workfront connector — OAuth fails for sandbox; org domain hardcodes .my.workfront.com
AnsweredWhich connector? Adobe Workfront
Additional details:
Environment
Fivetran destination: Snowflake — ADOBE_REVMKTG_PROD_SF_PRD
Destination schema: adobe_workfront_sb01 (sandbox)
Workfront org: ciscocomm
Sandbox host: ciscocomm.sb01.workfront.com
Production host: ciscocomm.my.workfront.com
Summary
The connector OAuth flow always targets {organization_domain}.my.workfront.com. Our OAuth app is registered in Workfront sandbox (sb01), not production. Authorization against the production host fails with "Application with provided client id doesn't exist." The same request against the sandbox host completes OAuth successfully.
We need a way to configure the Workfront environment segment (e.g. sb01) instead of the hardcoded my.
Steps to reproduce
Create/configure Adobe Workfront connector in Fivetran.
Set Organization domain to ciscocomm.
Enter OAuth Client ID and Client secret for our sandbox-registered app.
Click Authorize.
Actual result
Fivetran redirects to:
Workfront returns: "Application with provided client id doesn't exist."
Expected result
OAuth should target our sandbox host, e.g.:
https://ciscocomm.sb01.workfront.com/integrations/oauth2/authorize?...
With the same client_id, redirect_uri, and response_type, authorization and token exchange succeed (verified outside Fivetran UI).
Additional UI limitation
Setup guide says: if URL is https://myorganization.my.workfront.com, use org domain myorganization.
For sandbox (https://ciscocomm.sb01.workfront.com), there is no supported input:
Entering ciscocomm.sb01 in Organization domain is rejected: "Supports only [a-z0-9-_] characters."
No separate field exists for sandbox/environment identifier (sb01, etc.).
Business impact
We cannot complete Fivetran setup for Workfront sandbox data. Production Workfront sync is not an option for this use case. We are blocked on sandbox ingestion until the connector supports non-my Workfront hosts (or a configurable environment segment).
Request
Please add support for Workfront sandbox (and other non-production) domains, e.g.:
New field: Environment / Sandbox ID (sb01, etc.), or
Allow full hostname/org pattern so OAuth and API calls use {org}.{env}.workfront.com instead of always {org}.my.workfront.com.
-
Official comment
Hi Suresh Subramaniam,
Thank you for taking the time to share your detailed feature request regarding the Adobe Workfront connector. We truly appreciate your input and the clarity you've provided on the issue.
I'm pleased to inform you that your request has been added to our backlog. We understand the significance of this feature for your use case, and we are committed to addressing it as efficiently as possible.
Please rest assured that we will keep you updated on any progress or future developments related to this feature. Your feedback is invaluable in helping us improve our product.
Best regards,
Syead Mujtaba Imam Rizwi
Please sign in to leave a comment.
Comments
1 comment