Skip to main content
arrow-left Back to Docusign.com

Refused to connect to 'https://telemetry-d.docusign.net/api/v1/TelemetryWrapper' because it violates the following Content Security Policy directive: "connect-src 'self'

Is preventing render and im using v2 of the api

 

$recipient_view_request = new RecipientViewRequest((    'assertion_id' => $assertion,    'authentication_method' => 'none',    'client_user_id' => $userId, // must match with clientUserId set on the signer    'return_url' => $_SERVERR'HTTP_ORIGIN'] . '/coeus/?tab=success&signed=1', // Where to redirect after signing    'user_name' => $name,    'email' => $email,]);

@chenry - have you happened to resolve above issue? I am facing the same 

my demo code work before. our customer meet this issue yesterday. So I try it in my dev account and meet same issue. I have create case with support team and wait their update. 

 

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🏆 2024 APAC Reseller Growth Partner of the Year
🔧 The first in APAC to pass the DocuSign eSignature Technical Consultant certification.
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries.

Feel free to reach out for collaboration opportunities.

@Hengfeng Ge @chenry - I have same issue I try to fight since a week.. were you able to fix this?

 

@chenry @Kuba My environment is ok this morning. I don’t know whether there are any change in the DocuSign backend. but the support team also told me they are Ok, so I test it this morning.

 

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🏆 2024 APAC Reseller Growth Partner of the Year
🔧 The first in APAC to pass the DocuSign eSignature Technical Consultant certification.
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries.

Feel free to reach out for collaboration opportunities.

i am also facing the same issue while integrating docusign , attaching ss below 

 

Hi ​@rostwal could you provide the Json which you create the recipient url? 

we need the parameters: frameAncestors/messageOrigins.

 

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🏆 2024 APAC Reseller Growth Partner of the Year
🔧 The first in APAC to pass the DocuSign eSignature Technical Consultant certification.
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries.

const apiClient = new docusign.ApiClient();

apiClient.setBasePath(apiBasePath);

apiClient.addDefaultHeader("Authorization", `Bearer ${accessToken}`);

 

const envelopesApi = new docusign.EnvelopesApi(apiClient);

 

const viewRequest = new docusign.RecipientViewRequest();

viewRequest.returnUrl = "https://localhost:5173";

viewRequest.authenticationMethod = "email";

viewRequest.email = "signer@example.com"; // Same as signer email

viewRequest.userName = "John Doe"; // Same as signer name

viewRequest.clientUserId = "12345"; // Same clientUserId as above

viewRequest.frameAncestors = =

"https://apps-d.docusign.com",

"https://localhost:5173",

];

viewRequest.messageOrigins = =

"https://apps-d.docusign.com",

];

 

try {

const viewResult = await envelopesApi.createRecipientView(

accountId,

envelopeId,

{ recipientViewRequest: viewRequest }

);


this is my code for generating recipient url

 

Do you generate url every time when you load the focus view? Have you try copy the url in a new tab of browser whether it can load success?

 

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🏆 2024 APAC Reseller Growth Partner of the Year
🔧 The first in APAC to pass the DocuSign eSignature Technical Consultant certification.
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries.

yes , i generate new url every time , and yes it does open in browser tab 

 

Reply


Code of Conduct

Docusign Community

Code of Conduct