cdean | Posts: 18

Multi-signer package fails to return EXPIRED status after expiry datetime

0 votes

We create a package where Primary and Secondary signers are both true

We set the expiry datetime for 1 hour when we create the package

We process the package, then send the uploaded documents to OneSpan to sign the documents.

Each signer receives an email and a reminder email to sign the documents.

However, in the scenario where the Secondary signer COMPLETES the signing of the document online BUT the Primary signer does NOT sign the documents within the expiry date, OneSpan is NOT returning a status of EXPIRED.  

The reverse of this scenario works as expected and the retrieved package does return an EXPIRED status when the Primary signer signs but the Secondary does NOT.

Why does OneSpan NOT set the status to EXPIRED when the Primary signer does NOT complete signing the documents and the Secondary signer does complete signing the documents?

Thank you for any help or insights you can provide.

Clayton


Duo_Liang | Posts: 3776

Reply to: Multi-signer package fails to return EXPIRED status after expiry datetime

0 votes

Hi Clayton,

 

Please be aware that once the expiry date has been passed, signers should lost access to the Signing Ceremony immediately, but the package status will only be updated in batch, every 30 minutes (or 60 minutes depending on system settings). So it's possible that the package JSON didn't reflect the real status at the first place.

Back to your test cases, can you pull the package status once again where the Primary signer didn't complete signing the documents and see if the status is EXPIRED now?

 

Duo


cdean | Posts: 18

Reply to:

0 votes

Thank you for your quick reply.

Yes, I waited for the expiry date to hit which we have set for one hour.  After the one hour +5 to 10 min, I send the request to OneSpan to get all of the EXPIRED packages. The packages, that should have been expired after one hour, are NOT present in the OneSpan response.  The packages still have a status of SENT.  When we look at the packages from our OneSpan account the same packages' statuses are either still SENT or SENT (Trashed).  

Any ideas?

Here's how we are pulling requests from OneSpan, where packageModel is List<IdentifiPackageModel>:

const int PageCount = 50;
const int FromPackageNumber = 0;
const int PackageDaysRange = -7;

Page<DocumentPackage> Packages = OneSpanClientObj.PackageService.GetUpdatedPackagesWithinDateRange(status, new PageRequest(FromPackageNumber,                                                                                                                                                 PageCount), DateTime.Today.AddDays(PackageDaysRange), DateTime.Now);

foreach (DocumentPackage Package in Packages) {
    packageModel.Add(new IdentifiPackageModel { id = Package.Id.ToString(), status = packageStatus });
}


Duo_Liang | Posts: 3776

Reply to: Multi-signer package fails to return EXPIRED status after expiry datetime

0 votes

Could you share a package ID so that I can have a quick check for you?

 

Duo


cdean | Posts: 18

Reply to:

0 votes

Secondary signed only: srgrxf1LpUXTHr-XjBmyAdKTGcY=
Primary signed only :     seVvaTKO685acTjKKypeYWmehJU=

I just checked by polling OneSpan again and they are correctly set to EXPIRED now.
Is there a time difference between the OneSpan server and our east coast OLE Service that calls OneSpan?


Duo_Liang | Posts: 3776

Reply to: Multi-signer package fails to return EXPIRED status after expiry datetime

0 votes

Hi Clayton,

 

Expiry date in OneSpan Sign server is in GMT time, so if you pull the package JSON (GET /api/packages/{packageId}) and refer to the "due" attribute at package level, it's in GMT time which you can transfer to your local timezone and compare to your expectation. 

On the other hand, when you specify the expiry, you need to get the current GMT time first, then add 1 hour to the timestamp.

I will let you know if you found more in your packages.

 

Duo


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