223 results matched your search criteria
Forum topic
OneSpan Sign
Reposting from the .Net SDK channel
Issue:
It seems the issue is because eSignLive is anticipating that the ‘Id’ of the group is the GUID that identifies
Forum topic
OneSpan Sign
Hi,
I am trying to create a document with editable field which user will fill it out. But I cant find how to do it.
Forum topic
OneSpan Sign
We are facing an issue with third party cookies in Safari and in other browsers where the users have the third party cookies disabled.
Forum topic
OneSpan Sign
Reading these two documents:
https://www.onespan.com/blog/onespan-sign-developers-consent-document-vs-default-consent-part1
https://www.onespan.com/blog/onespan-sign-developers-consent-document-vs-default-consent-part-2
Forum topic
OneSpan Sign
I am making good progress on my project I am now at a point were I want to have my app download the document after the signing is complete.
To do this I would like to set up a call back event on PACKAGE_COMPLETE
My dev environment is local 127.0.0.1 with a local host name How can I test the call
Forum topic
Intelligent Adaptive Authentication
Helo,
Inside my product ecosystem, I have already wso2 Identity Server up and running which provides GWT token. I am willing to use the MFA capability of Onespan and the push notification as a reliable solution instead of OTP.
Forum topic
OneSpan Sign
When we have a package that has two signers and one signer has completed signing and the other is still pending, when we perform a check status, we are getting the following error.
Could not get signing status. Exception: The remote server returned an error: (404) Not Found.
Forum topic
OneSpan Sign
Hi guys,
I was testing how to call OneSpan api from POSTMAN using this steps mentioned in this link but I keep getting this error message:
There was an error connecting to https://sandbox.esignlive.com/api/packages/.
Forum topic
OneSpan Sign
I'm seeing some odd behavior, on my local development environment, I can create a package and delete the "default-consent" page without issue. Once I've moved this to our integration environment, this same call fails.