EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Signature seems to be signed in future

Also by EldoS: CallbackFilter
A component to monitor and control disk activity, track file and directory operations (create, read, write, rename etc.), alter file data, encrypt files, create virtual files.
#20824
Posted: 07/18/2012 07:30:15
by bruno jeanjot (Standard support level)
Joined: 06/19/2012
Posts: 11

I have a signer PDF program (base on TinySigner sample) that runs perfectly for some years now.

Recently, I improved the program to support signature on landscape document; therefore, I get your support to rotate the signature stamp; I needed to upgrade from my old version 5.2 to version 6.1. This solved my stamp rotate problem.

But ... it now appears that any signing document raised an error when opened in acrobat reader (I use version 9.5.1).
" Signature seems to be signed in future"

My code is as follows
Sig.WidgetProps.ShowTimestamp = True
Sig.SigningTime = DateTime.Now

If I changed my assignment to
Sig.SigningTime = DateTime.Now.ToUniversalTime()
this is OK BUT THIS IS NOT WHAT I WANT

I want to display local time (that is GMT+2 now is Belgium) and not UniversalTime.
#20825
Posted: 07/18/2012 07:45:29
by Ken Ivanov (EldoS Corp.)

Bruno, thank you for getting in touch with us.

Please add the SBPDF.Unit.aoAdjustTimesToUTC flag to the TElPDFDocument.AssemblyOptions flag set. This should make the components act in the way you want them to.
#20826
Posted: 07/18/2012 08:23:26
by bruno jeanjot (Standard support level)
Joined: 06/19/2012
Posts: 11

I tried to insert the following code after my document creation
Document = New TElPDFDocument
...
Document.AssemblyOptions = SBPDF.Unit.aoAdjustTimesToUTC


but this member is unknown !

(only aoAcrobatFriendlyAcroForm is available)
#20829
Posted: 07/18/2012 09:26:38
by Ken Ivanov (EldoS Corp.)

Indeed, this option was only added in SBB 7, thus it is not available with SBB 6. I am afraid, there is no way to specify signing time in 'local' (not universal) form with SBB 6, sorry.
#20830
Posted: 07/18/2012 09:40:45
by bruno jeanjot (Standard support level)
Joined: 06/19/2012
Posts: 11

I am a little bit surprised.
Because I never have this problem with version 5.2
It only appears when using version 6.1.

Using version 5.2 the code
Sig.SigningTime = DateTime.Now
produce a timestamp in local time without error when opened in Acrobat.

Why do I get an error with the same code when using version 6.1?
How is it possible to avoid it?

Thanks
#20831
Posted: 07/18/2012 10:32:53
by Eugene Mayevski (EldoS Corp.)

There were certain reasons to *change* behavior in version 6, and after some users requested for an option, it was added. As the option was added only in version 7, this is a good indicator of very limited need for it.

In your particular case there are three obvious options available:
1) rollback to version 5
2) accept the behavior of version 6
3) upgrade to version 9 with free update to version 10 when it's out


Sincerely yours
Eugene Mayevski
#20836
Posted: 07/19/2012 03:41:10
by bruno jeanjot (Standard support level)
Joined: 06/19/2012
Posts: 11

Thinking about it again, I conclude that version6 store the SigningTime in UTC. So I need to change my V5 code
Sig.SigningTime = DateTime.Now
to
Sig.SigningTime = DateTime.Now.ToUniversalTime()

That's OK.


But now, I would like to display local time in the Signature appearance.
How can I achieve this?
#20837
Posted: 07/19/2012 04:33:11
by Eugene Mayevski (EldoS Corp.)

Knowing that the signature time is in UTC you can perform backward conversion. As for Acrobat and Adobe Reader - that's a question which should be directed to their developers, not us.

In SBB 7 and later you have an option to control this appearance.

I don't see any point in discussing this further. All possible options have been mentioned above, and you can choose the one you prefer.


Sincerely yours
Eugene Mayevski
Also by EldoS: Callback File System
Create virtual file systems and disks, expose and manage remote data as if they were files on the local disk.

Reply

Statistics

Topic viewed 1943 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!