Skip to main content
Newcomer
Nov 9, 2026 10:00 PM UTC
Question

Embedded sending blocked in Demo (frame-ancestors) – Oracle Fusion Enterprise Contracts integration

Hello,

We are testing the standard Oracle Fusion Enterprise Contracts integration with a DocuSign developer (Demo) account. The connection is validated in Oracle (OAuth consent granted, status Complete), but sending a contract for signature fails.

What happens:
- Oracle opens the DocuSign sender view inside an iframe.
- The browser blocks it: "Framing 'https://apps-d.docusign.com/' violates the following Content Security Policy directive: frame-ancestors 'self'".
- The iframe URL is https://apps-d.docusign.com/api/send/auth-from-console-1ds?code=...
- Opening that URL in a separate tab returns: "Login Unsuccessful – redeem console code : RestApi Error". Transaction Id: aae72005-26c5-4159-a080-2466898c9c88
- No envelope appears in the account's Drafts.

This looks similar to the issue reported on the community forum since 21 Oct 2026 ("Focused view / embedded signing blocked since ~21 Oct 2026 – redirect to apps-d.docusign.com/authenticate has frame-ancestors that ignores frameAncestors").

Questions:
1. Is this a known regression in the Demo environment, and is a fix planned?
2. Does the same behaviour apply in production?
3. Is there an account-level way to keep the sender view embeddable until it is fixed?

Demo account ID: [d*******-****-****-****-**********20]
Date/time of the test: 09/11/2026, around [22:40] (Europe/Paris)

Thank you,
Kenny K*****
Kaora Partners