在iFrame中嵌入文件签名仪式时,有谁遇到过问题吗?我正在尝试使用iFrame来测试签名。但是浏览器(tested on Chrome, Firefox)拒绝呈现url。
我从DocuSign获得嵌入url (看起来像DocuSign),然后在我的网站上将这个url设置为iFrame源代码。但是它只是显示一个空白页,什么也没有出现(而不是嵌入到iframe中,如果我只是将url粘贴到url栏中,它就会呈现精细的)。如果我检查Google中的控制台日志(在win10上),就会看到一个错误
Refused to display 'https://account-d.docusign.com/recipient/auth?ui_locales=en' in a frame because it set 'X-Frame-Options' to 'sameorigin'。
<iframe src='https://demo.docusign.net/Signing/MTRedeem/v1/XXXXXXXXX?slt=XXX' height='900' width='900'>
</iframe>

如果我观察到网络选项卡,就会发生以下重定向:
Request URL: https://demo.docusign.net/Signing/MTRedeem/v1/XXXXXXXXX?slt=XXX
Request Method: GET
Status Code: 302 Found
Response Headers
Location: https://account-d.docusign.com/managed_token/v1/redeem/?slt=XXX
Request URL: https://account-d.docusign.com/managed_token/v1/redeem/?slt=XXX
Request Method: GET
Status Code: 302 Found
Response Headers
Location: https://demo.docusign.net/Signing/StartInSession.aspx?code=XXX
X-Frame-Options: SAMEORIGIN
Request URL: https://demo.docusign.net/Signing/StartInSession.aspx?code=XXX
Request Method: GET
Status Code: 302 Found
Response Headers
Location: https://demo.docusign.net/Signing/ActivateSecurityChecks.aspx?insession=1&ti=XXX
Request URL: https://demo.docusign.net/Signing/ActivateSecurityChecks.aspx?insession=1&ti=XXX
Request Method: GET
Status Code: 200 OK
Response Headers
Set-Cookie: BIGipDocuSign_Demo_Signing=XXX
X-DocuSign-Node: XXX
Request URL: https://account-d.docusign.com/recipient/auth?ui_locales=en
Request Method: GET
Status Code: 200 OK
Response Headers
X-Frame-Options: SAMEORIGIN
X-DocuSign-TraceToken: XXX
X-DocuSign-Node: XXX注意:我遵循了docusign的官方示例中的https://github.com/docusign/eg-03-csharp-auth-code-grant-core/blob/master/eg-03-csharp-auth-code-grant-core/Controllers/Eg001EmbeddedSigningController.cs示例。
编辑 RecipientViewRequest:
{
"AssertionId":"logging in event id",
"AuthenticationInstant":"1\/29\/2020 11:09:26 AM",
"AuthenticationMethod":"password",
"ClientUserId":"logged in user id",
"Email":"my-email@mydomain.com",
"ReturnUrl":"https:\/\/subdomain.mydomain.com\/recieve",
"UserName":"signerFirst lastName",
"XFrameOptions":"allow_from",
"XFrameOptionsAllowFromUrl":"https:\/\/subdomain.mydomain.com"
}编辑2
如果我还记得的话,在过去的测试中,嵌入式方法曾经对我起过作用。这种拒绝在iFrame中呈现的行为是最近才开始的。也许他们在上个月的时候变了。
发布于 2020-01-29 16:07:48
一般来说,由于兼容性和故障排除困难,iframes是不被鼓励的。建议将用户重定向到URL,然后在完成后捕获returnUrl重定向。
也就是说,在信封::CreateRecipientView调用中有两个相关的参数
"xFrameOptions": "allow_from",
"xFrameOptionsAllowFromUrl": "https://example.com"其中xFrameOptions参数应该是"allow_from“来启用此功能,而AllowFromUrl应该是站点的域。
https://stackoverflow.com/questions/59970661
复制相似问题