+1Long story short, I had an embedded E-Signature set up and working without issue last month. Now it only works on my staging server and not on my local. Locally I’m receiving the screenshotted error in my console along with many more. I’ve been trying to work through it with google and other posts be am getting no where and falling behind on my development schedule. Any assistance would be greatly appreciated.
Thanks,
Andrew
Hi
From the console output, it appears that this is a Content Security Policy (CSP) configuration issue affecting embedded signing locally.
Ensure your createRecipientView request includes the exact local origin (scheme + host + port), for example: http://localhost:5173, in frameAncestors, and includes the Docusign domain for your environment (apps-d.docusign.com for sandbox; apps.docusign.com for production). Also, set messageOrigins to the same Docusign domain for your environment. These values are required for focused/embedded signing to render inside your page.
For guidance, please refer to the following document: https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view/
If you continue to see the error, please create a case with Docusign Developer Support
Hope that helps
Best regards,
+1Hello
I have updated my code to ensure the frameAncestors object is set when creating the recipient view. Alas I’m still experiencing the issue and cannot move forward. In fact nothing on the console has changed. I’m not sure what the issue could be at this point as I’ve added domains that should work. Is there a way to see what DocuSign is seeing as the host when I send it? Not being able to fix this quickly is very frustrating.
Either way, thank you for your time and response. Hopefully I can get this figured out sooner than later.
-Andrew
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Back to Docusign.com
