tlolkus's account

Is or will this fix be available for those running OneSpan on prem?  We run OneSpan on prem and we are in the process of trying to integrate the designer using an iframe and came across this issue.  If it is available can you let me know what version?  We are currently developing against an older version but we just spun up a new server with 7.2. but I suspect we may need a more recent version.

Thanks,

Tricia

Good Morning Duo,

Just to confirm when I try to access the designer in an iframe it does not load and within developer tools I see the following error:  

Refused to display 'https://servername/a/login?destination=/a/transaction/NLSGgqHCjJKL09UqKDE5-BJCk2Y=/designer' in a frame because it set 'X-Frame-Options' to 'sameorigin'. 

I am running the latest version of Chrome (84.0.4147.89). 

I did a couple of things to confirm it appears to be the same issue.  

1) Within Chrome settings, under cookies and other site data I did change my option to 'Allow all Cookies' and that did not fix the behavior.

2) As you also recommended, I pointed our environment to the sandbox which is running 11.35 (https://sandbox.esignlive.com/)  I did this using the same settings that did not work against our On Prem version and I was able to load the designer in an iframe. 

3) We also pointed our dev environment against our newest One Span Stage environment (remember we are running On Prem) which is 7.2. and I am still seeing the issue where I cannot load the designer.  

4) After reading many articles about this Chrome change, I also went into my Chrome flags (chrome://flags/) and searched for a flag called 'SameSite by default Cookies'.  Mine was set to Default.  I changed it to Enable and I continued to see the behavior where the iframe would not load.  When I changed it to disable then the iframe did load.  I think this confirms that this setting is causing the issue. 

Here is a good reference for the Chrome Samesite changes they just started gradually rolling out on July 14:  https://www.chromium.org/updates/same-site

So now the question is how to we get the fix that was implemented in your Saas in our on Prem version?  Correct me if I am wrong but I believe this is the fix for the issue, which I found in your published release notes.

• PB-40750: Removed a cookies warning that needlessly appeared when the Designer page was integrated in an iFrame on Chrome 80.

I greatly appreciate your help on this matter.

Thanks,

Tricia

We are looking to customize our Designer view as we are integrating OneSpan using an iFrame.  I see that most of the documentation indicates that you need to contact support to either customize your default profile or create new profiles.  We run on Prem (version 7.2) so is this something we can do ourselves or does it still require help from support?  If we can do it can you provide some documentation?

Here is the article that is guiding me:

https://www.onespan.com/blog/onespan-sign-developer-designer-customization-and-integration-part-2

Has the issue of setting the Expiration Date to null been fixed in the .Net SDK yet or is it scheduled to be fixed?  We are running 7.2 on Prem and still seeing this issue.  We have implemented the workaround but this requires some ugly code on our side.

We ended up opening a support ticket and they helped us with this process.  

Thanks for following up!