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

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

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 });
}

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

Duo

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?

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

Thank you for the explanations.
These are very helpful.