Reading Signed Document

Hi all,
I download a signed file to local with extension .p7s.
I've signed the document in server with FM SSF_KRN_SIGN_BY_AS.
If I open the downloaded file in my pc, I can see the Certicate which has signed the doc, but if I open the certificate there is a warning saying that Windows hasn't enough information to verify the Certificate...
If I sign the doc with my local app or using FM SSFS_CALL_CONTROL, I can see in downloaded file my Certificate, and a tree with the CAs that certificates my Certificate...
Why in the first way can't see that CAs tree? How can I see it to get the sign be ok?
Thanks in advance.
Regards.
Urtzi.

Well, when using SSFS_CALL_CONTROL the digital signature operation is perform on the frontend (see ABAP program SSFSDEMO for an example).
When using SSF_KRN_SIGN_BY_AS, however, the digital signature operation takes place at the application server (AS).
When performing the digital signature operation on the frontend you are using one of the certificates (with corresponding private key) which are present in the keystore at the frontend PC. Microsoft Internet Explorer and the Microsoft Windows operating system are using the very same keystore - therefore it's not surprising that you'll be able to display the complete trust chain / tree (if the chain would be incomplete you would not have able to perform the digital signature operation).
Most likely the certificate used at the backend is self-signed. In that case it's not surprising that you fail to validate the certificate at the frontend. The situation would be different if the certificate would have been issued by a CA whose root certificate is present in the keystore of the frontend PC.

Similar Messages

Appending new pages to signed documents now makes Acrobat 9 and Reader 9 mark signature as invalid

Hello!
I have developed a service that appends additional pages to existing PDF documents. Some of the documents the service works on happen to be signed. As the service appends the pages using incremental updates, the signed contents are left untouched. This makes Acrobat 8 and Reader 8 display the signature state as "valid with subsequent changes" which is ok and no one complains about.
Now along come Acrobat 9 and Reader 9, and all of a sudden the signature state is "invalid" which my users do complain about. Telling them that inspecting the signature state details they can see that the signed content still is untouched and the actual change is recognized to be some appended pages, doesn't help either as they in turn forward the documents to their customers who don't accept the documents if the Adobe Reader sais the signatures are invalid.
Does anyone know a way new pages can be added to a signed document without having the new Adobe program versions choke on them?
Even a hint that involves adding some flag to the original unsigned document or the signature itself would help as the users in question can tweak those processes. Due to the nature of the workflow, though, signing unfortunately must happen before my service can add the new pages.
Best regards, Mikel.
By the way, the signatures in question are regular approval signatures, nothing fancy, especially not certifying signatures (which indeed can forbid any changes or at least any changes but some form fill-ins and annotations)...

Hi Fritz,
In the interest of full disclosure, I got the answer to the problem from one of my distinguished colleagues, I'm just the messenger in this case.
The problem is that the form adds some items to the Arzneispezialität / Zusatztext combobox which are there during signing but the form doesn’t remember that it did this on the next form open.
Since this field is included in the MDP+ signature and the field has changed in the re-opened version vs. the signed version, the MDP+ signature becomes invalid.
XFA has a feature that remembers these kinds of things for you but it is turned it OFF. Please open the attached screen shot to see the control in question.
So, you can either (1) turn this feature ON (Automatically), or (2) write some script to clear the combobox items prior to signing or (3) write some script to repopulate the combobox items on the subsequent open to match the items that were there during signing.
Steve

Why is the "Sign Document" option not available in Reader 9.1?

When I open a PDF in Reader 9.1 the "Sign Document" option is grayed out (unavailable) Is this option dependent on which version of Adobe Acrobat was used to create the PDF? As a test, I created a PDF in Acrobat Standard 8.1. I can sign the that PDF in Acrobat Standard 8.1 but I cannot sign the same PDF in Adobe Reader 9.1.

I have adobe reader 9.1 and want to sign some documents. The sign option isn't available and I don't have Acrobat professional. Does that mean I can't use the free digital signature add-on?
Thanks.

I have an iMac and have been using Adobe reader successfully for sometime. Recently, however, whenever I go to sign a document on Adobe reader The document closes unexpectedly with an error statement. I have already uninstalled and reinstalled Adobe reade

I have an iMac and have been using Adobe reader successfully for sometime. Recently, however, whenever I go to sign a document on Adobe reader The document closes unexpectedly with an error statement. I have already uninstalled and reinstalled Adobe reader with no improvement. What do I do next?

Please post the full error message, plus OS and Reader versions.

Cannot sign documents with Adobe Reader 10.1.3 - 10.1.10, Can sign document with 10.1.2 and 11.0.07

Cannot sign documents with Adobe Reader 10.1.3 - 10.1.10, Can sign document with 10.1.2 and 11.0.07
In my environment, we have 10.1.2 that's currently packaged. Our CIO was able to sign documents via signature with no problem. Later he got updated to 10.1.9, no longer can sign.
During testing I was able to confirm that 10.1.2 signed without problems, but anything that, it goes kaput, the Sign and options are not listed.
Latest Adobe Reader can sign... any ideas?

I'm having a similar problem. What I'm trying to do is print a Microsoft Word 2010 document with paper size A4 to Adobe pdf document paper size A4. I select "A4" for paper size in word and then print using Adobe print standard settings. What I get is an Adobe document in 8.5 x 11. This is an issue because these are patent documents for electronic filing in WIPO and they must be in A4 size.
If I select other sizes in Word, such as A3, Tabloid, and Legal, the Adobe file is in the same paper size.
If I print a Powerpoint document in A4 to Adobe, the Adobe file page size is A4.
If I print an Adobe file in 8.5 x11 to Adobe A4, the second Adobe file is in A4.
Any help?

When printing a signed document with Adobe Reader, the comment icons appear. How do I prevent this

When printing a signed document with Adobe Reader, the comment icons appear. How do I prevent this ?

When printing from Reader, select Document instead of Document and Markups:

Reader Extend Feature for sign document

If you like to sign the PDF document in Reader, please apply Reader Extend feature from Acrobat product first and save the file, and then you can sign the document in Reader.
Some user will sign the document first and apply Reader Extend feature later, this workflow will break the sign workflow.
Thanks for Acrobat product customers to use the product and give us this useful feedback.

Something happened to the file after the time that it was Reader-enabled. It was modified in a way that invalidates the digital signature that controls whether the usage rights are valid. I seem to recall the GoLive can be configured to modify (optimize somehow?) PDFs when it uploads them, and you definately don't want this to happen for Reader-enabled documents. I don't have GoLive, so I can't check what setting it is, but you should be able to look for yourself. A workaround would be to upload via some other means, such as FTP. I'd be interested to know if this makes a difference.

Adobe Reader XI- Trouble with signing documents

I can't sign documents with Adobe Reader XI. I have registered for Echosign (unwillingly) and also created an identity. The signature field is grayed out. I have tried several different documents. Some documents un-gray the signature option, but it does nothing when I click it. Please advise.

I had the same problem , but in my case it was caused by the document properties would prevent unsigned signature fields from being signed.

There was a problem reading this document (117)

Dear Designers
I am facing a strange problem while doing test presentment in Adobe output designer. When i do a test presentment with my dat file which is meant for fax (^job newFax -fform01F.MDF) , i see the pdf (consist of 2 pages ) but as soon as i scroll down to next page (Pg 2) of my pdf ; it giving me a Adobe reader error pop up "There was a problem reading this document (117)" and when i click OK and comes to page 2 (i'm seeing the content of Pg2 curerntly) and scroll back to page 1 the data on page 2 goes blank. What could be the possible reason for this ? I assume the flaw is on Adobe reader side , but please brighten me with the knowledge if there is some issue on dat file side.
Any possible guidance or help would be highly appreciated
thanks
jaY

Sorry, I do not quite understand what your problem is:
you have a problem with signing in to the ExportPDF service ?
you have a problem opening PDF files ? If so, are these local or online documents?
P.S. Reader XI and earlier will no longer support Document Cloud PDF services as of May 20; see https://forums.adobe.com/docs/DOC-5891

'error while signing document'

i got this error ('error while signing document') on my 1st attempt to use the service. simple 4 page PDF, no doc. security, same error both b4 & after i edited my user profile (i filled in the missing details & changed the default signature image).
cheers,

Hi,
I am also getting this error while attempting to sign a document. I have checked the first and name fields in my default signature profile for any non-English characters but I am still getting this error. I have also tested with a different signature profile with same results. Please advise if there are
other fields I need to check.
Thanks.

There was a problem reading this document (118) after sleep

Adobe reader X 10.1.8.24, windows 7 64 bit
I have a lot of pdf documents located on a remote windows share and everytime I put my computer to sleep and wake it up I get problems reading pdf documents that result in this error:
There was a problem reading this document (118)
Then I have to close ALL pdf documents and re-open them to be able to read them again.
This has happened for a long time now, with multiple reader versions and it really starts to bother me. Other applications just pick up the remote files where I left them before putting the pc to sleep. The reader should be able to retry getting the data from the remote share.
Where do I report this bug?
Jur.

Sorry, I do not quite understand what your problem is:
you have a problem with signing in to the ExportPDF service ?
you have a problem opening PDF files ? If so, are these local or online documents?
P.S. Reader XI and earlier will no longer support Document Cloud PDF services as of May 20; see https://forums.adobe.com/docs/DOC-5891

Links no longer work after signing document

Links no longer work after signing document - I have updated to latest version and run installation repair, is this a problem or is it supposed to do that?

Hi;
This question would be best asked in the Acrobat signatures Forums, it is related to using Adobe Acrobat/Reader and does not have anything to do with the online service, Adobe Fill & Sign. Someone should be able to answer your question here: https://forums.adobe.com/community/acrobat/security_%26_digital_signatures
Thanks,
Josh

When saving a signed document can the -signed appellation be turned off?

When you go to save a document which you have digitally signed, the program automatically appends '-signed' to the end of the file name. This is not ideal for my purposes - is there any way to turn this function off? Also it it possible to turn off the prompt that asks me if I'd like to email the signed document? I've gone through every screen in preferences but I can't seem to find anything for this. I'm using Adobe Reader XI 11.0.5.
Thank in advance!

Not that I know of. Reader and Acrobat want you to have a new copy of the signed document and an original copy of the unsigned version, hence the behavior you do not want. You can always do a save change the name of the signed document to the original name if you desire.

Update 9.1.2 breaks digital signing documents in Adobe 9 Pro on Windows XP

I am able to digitally sign documents using an Aladdin eToken Pro 64k with a fresh copy of Adobe 9 Pro for Windows. However when I update to version 9.1.2 digital signing fails with an "error encountered while BER decoding". Signing still works on Vista and Adobe 9.1.2 Pro. I've checked to make sure none of the settings relating to digital signing changed during the update and none have. Anyone have any ideas on how to correct the problem?

Hi Nick,
First up, there was a small error in my previous post. I said the version of Acrobat (and whenever I say Acrobat I really mean both Acrobat and Reader, but I'm too lazy to type both) that was modified to fix the bug in SHA-1 fallback was 9.1.3, but I really meant 9.3. Sorry about that.
I saw your post from yesterday (http://forums.adobe.com/thread/563601) where you broached the BER decoding error, but in the post above you said signature creation isn't failing any more, so hopefully some update has fixed the problem.
Here's a little bit about the BER Decoding error. During the signing process Acrobat writes the entire file to disk (which is why you always get the Save As dialog as part of the signing process) in the signed state with everything but the actual signature. However, it does leave a hole in the file where the BER encoded cryptographic data will reside once it's be computed and formatted. One thing that is created before the actual signature is the signature appearance. The signature appearance in the form field isn't really the signature proper, but just a graphic representation of the actual signature. The reason that the signature appearance is written to disk before the signature is created is because it too is part of the signed data and must exist before the actual signature is created.
In a perfect world, after the file is written to disk, the cryptographic signature is created and written into the hole in the PDF file, and the signing process completes without any problem. However, if we get to the point that the file has been written out, but during the actual signature creation the process fails, that hole I mentioned isn't filled in. It's not really a hole per se, but a block of zeros that act as a placeholder for the BER encoded data. Because there was some sort of failure and Acrobat didn't get the signed data back from the hardware device what you end up with is a PDF file with a signature appearance, but no real signature in the file. When you click on the signature field Acrobat tries to validate the actual signature, it finds the block of zeros where the signed data was supposed to be, it tries to decode the zeros and gets (as you might well imagine) nothing back and displays the BER Decoding error.
Let leaves us with why didn't Acrobat get the signed data back. When using hardware devices, such as tokens or smart cards, the actual cryptographic signing (the encryption of of the digest with the users private key) takes place on the device. Acrobat (nor any other application) doesn't have access to the private key, which is what makes hardware devices more secure. It's up to the device to sign the data and send it back. If there is any kind of breakdown in that communication channel (which I mentioned in my previous post) the signature creation doesn't reach fruition and you're left with an unsigned file that looks like it was signed because there is a signature appearance.
This is a case where we are providing technically correct, and utterly useless information. It's true that we can't decode a bunch of zeros, but what we should be telling the user is there is no signature (it's kind of like the Matrix where there is no spoon ).
I hope this helps explain what you're seeing. If the the signing process breaks down again please make sure you are using the latest version of Acrobat/Reader and the token software is up-to-date. If everything is current and the problem returns please let me know.
Steve

The "sign document" function is not working in Adobe Acrobat X 10.1.8?

I had an issue with Adobe Acrobat erroring with an error message relative to the Crypto file in Windows. I attempted to do the file folder renamaing to 'old', etc. to no avail. When I tried to restore everything to it's original state, the sign document window appears (see below), but when I click on the sign document buttone, nothing happens at all. I have tried this in multiple documents, through multiple siging routes, and all the same non-result. I have also reinstalled Acrobat to no avail; advice?

This is the Reader forum; the Acrobat one is here:
http://forums.adobe.com/community/acrobat

Reading Signed Document

Similar Messages

Maybe you are looking for