peterzog | Posts: 109

Source Page - Keep Alive

0 votes

We allow users to click a sign button on a page that expires rather quickly (2 minutes) and it opens OneSpan in an external browser tab. Does OneSpan have a feature to ping an endpoint during the signing ceremony to keep the session alive on the source page? 


Duo_Liang | Posts: 3776

Reply to: Source Page - Keep Alive

0 votes

Hi Peter,

 

If you are directly visiting the signing ceremony, I doubt OSS has the ability to ping an endpoint and keep the other tab's session alive. But you can either embed the signing ceremony in an iFrame and keep session alive behind the scene, or you can try to leverage the handover URL after completion and grant the browser session again (I didn't have a chance to verify this but it's an idea came out of my mind).

 

Duo


peterzog | Posts: 109

Reply to: Source Page - Keep Alive

0 votes

Thank you for your comments, Duo. I relayed your thoughts to the team and I am still getting pushed to pursue the keep alive feature since "we have this pattern with other our vendors". Apparently, it's not unprecedented with integrating third party vendor services to our client portal.

How about this question, are there best practices that OSS has for implementing with client portals? 

Thank you as always,

Peter


peterzog | Posts: 109

Reply to: Source Page - Keep Alive

1 votes

Just updating this thread to include this article for others to reference: https://www.onespan.com/blog/onespan-sign-developer-session-expiry-iframe

 

 


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off