Multiply digital signature in document - prevent save after each

Is there a way to prevent acrobat 8 from saving after each signature. I want to place there separate signatures on a document have the individual sign all then save.
current adobe acrobat pro 8.1.2

My two cents:
When you sign a document, Adobe creates a bit-count or parity-check of the document in the state it was when it was signed. That's why it was saved. It has to detect whether the signed version was altered in any way. The signature is tied to the document very intimately.
If I change some part of a document after I sign it, the bit-count changes and the signature gets flagged.
However, I have the same problem. I have a purchase request that needs to be signed by the requestor, the department head, finance, blah, blah, blah... Each time the latest signatures look great and the previous ones are flagged. I thought Version 8 was capable of just defining what fields are authenticated by the signature, but I haven't fount it yet.

Similar Messages

Java SSF for Digital Signatures and Document Encryption

Hello,
I have read in "SAP Help - Java Development Manual" that there is a Java SSF library for Digital Signatures and Document Encryption API.
http://help.sap.com/saphelp_nw04s/helpdata/en/4f/65c3b32107964996a56e4165077e24/frameset.htm
I am trying to develop an example application in NWDS using Interfaces/classes (ISsfData, SsfDataXml...), but NWDS does not find this classes in any library.
I have searched for Javadocs in NWDS plugins directory and this classes and interfaces should be in JAR com.sap.security.api.jar, but they aren't there.
Our WAS version is: NW04s WAS 7.0 SP11 and he have downloaded Java Crypto Library (IAIK) and also SAP XML Toolkit.
Does anyone know how to find or obtain this library?
Thanks in advance,
Jorge Linares

Hello Francesco,
I want to generate a digital signature (PKCS#7,XML) using SAP SSF API as explained in
http://help.sap.com/saphelp_nw04/helpdata/en/4f/65c3b32107964996a56e4165077e24/content.htm and in Amol Joshi's reply in
Digital Signatures and Document Encryption api
so my question is From which PI/XI version and its SPS this SAP SSF LIBRARY is supported ?
Kind Regards,
Kubra fatima.

Digital Signatures and Document Encryption api

Hello Expert,
From which SAP NETWEAVER 7.0 SPS Digital Signatures and Document Encryption api is supported ?
I found Javadocs for SAP NetWeaver 04 SPS15.Is this api supported from SPS 15 or prior to SPS 15 also?
Regards,
Kubra Fatima.

Hello Francesco,
I want to generate a digital signature (PKCS#7,XML) using SAP SSF API as explained in
http://help.sap.com/saphelp_nw04/helpdata/en/4f/65c3b32107964996a56e4165077e24/content.htm and in Amol Joshi's reply in
Digital Signatures and Document Encryption api
so my question is From which PI/XI version and its SPS this SAP SSF LIBRARY is supported ?
Kind Regards,
Kubra fatima.

Digital Signatures - how to prevent anyone from using my name

I've created a bunch of forms that have digital signatures enabled. When I've created one either with the PKCS or the Windows Certificate, what's to prevent anyone else from just typing my name, email address and Company Name? Yes, I can create one and save it with a password, but anyone can do that. I'm confused how I can ask our users to use digital signatures on internal documents, then have them email to accounting or HR, yet there's nothing to prevent anyone from using anyone else's name (ie how can I prove that it wasn't me that signed it)?
Is there nothing that's tied to Windows ie I can't use my login ID on our domain unless I use my network password? That's really the ONLY way I can prove I'm me.

Self-signed digital signatures are precisely that - the person creating them is the only one attesting to the contents, so you can make a perfectly-valid self-signed ID for Canta Claus of you want to. The critical thing to remember is that a self-signed ID will only validate if the recipient has your keyfile to compare it to. On your own machine it will show as valid because the key is present, but if you send the PDF to anyone else it will show as invalid unless you have separately transferred them a copy of your keyfile. It's that second file which tells them the ID is really yours, as they can physically check where it came from (e.g. by phoning you up). The recipient would then have to manually add the keyfile to the trusted list in Acrobat or Adobe Reader, and finally your PDF signature will get the green tick.
Self-signed IDs are find for internal company workflows as everyone can share their keyfiles, and the IT department can manage what's going on. If you're using digital IDs in a public setting you should never use self-signed certificates, instead you should purchase an ID from a Certificate Authority - a company whose IDs are tied to the 'root certificates' embedded in Acrobat and Adobe Reader. The CA will require proof of identity before selling you the cert, and so anyone can verify it's genuine without needing to contact you. CAS-issued certs for signing PDF files are not cheap, there are several vendors out there and I won't comment on which may be better.

Digital Signature error - "Document could not be signed"

I have a servlet (from the documentation sample) the rendered my form online. My form was saved from Designer as Acrobat 7.0.5 Static PDF Form File and then I applied Reader Extensions to it to allow for Digital Signatures and Basic Form Fill In. When I try to digitall sign the form, I get the error:
"The document could not be signed."
"There was an error when attempting to commit this signature. The document was not saved."
"A file error has occurred."
Anyone know what this means and how do I fix it??
I am using Acrobat Reader 7.0.8, so maybe that is the problem, but I won't know what version Reader my user's will have, so it needs to work in many versions.
If I don't sign the form, I can submit it where a second servlet saves the form to a file and this happens successfully.
Thank you,
Jennifer

Hello Rob,
Thanks for the reply.
Actually, there is a bug with Reader and Form Rendered forms - at least with already extended pdf forms that get rendered via Form Server.
So, I hope this makes sense, but this is what I have determined (this is all done with viewing the EXTENDED PDF form WITHIN a WEB BROWSER):
If I use a simple hyperlink (i.e. plain html anchor tag) to my PDF form, I can digitally sign the form with no problem within in all 7.x versions of Reader.
If I utilize Form Server code (tested with local EJBClient and then remote JBoss using SOAPClient) then the results vary:
Reader 7.0.0 - I could successfully sign the form
Reader 7.0.5 - I could successfully sign the form
Reader 7.0.7 - I could NOT sign the form
Reader 7.0.8 - I could NOT sign the form
Reader 8.0.0 - I could successfully sign the form
So, you can see in version 7.0.7 and 7.0.8, one cannot digitally sign a form if it was rendered via Form Server and viewing the form in the web browser, but I can sign it just fine if I display the form via a simple html hyperlink, so that is what I am doing now.
I had this same issue when using Workflow server, but that was easy enough to apply the Reader Extension QPAC over and over as needed. I need these forms to be submitted on a remote server and haven't figured out yet how to apply the Reader Extension remotely yet.
I hope this helps.
Jennifer

Digital signatures on documents

A requirement from our user community is to have legally binding signatures on documents stored as content. Looking through the online documentation, it doesn't appear that the functionality is "out of the box". Has anyone out there ever done this before? If so, how?

What does the details button reveal?

Add Digital signature to document

Hi,
I want to add digital signature to the doccument. E-signature is possible how about this?
Thanks,
Jai

Check below -
http://docs.oracle.com/cd/E28280_01/bi.1111/e22255/digital_sig.htm
http://docs.oracle.com/cd/E12844_01/doc/bip.1013/e12187.pdf
Cheers,
Vignesh

Digital Signature in Document Signature field slow

The business requirement is for users to digital sign a Dynamic PDF. Digital ID's are created using Advanced - Security Settings - Digital ID - Add ID - Create a self-signed digital ID for use with Acrobat - New PKCS#12 digital ID , from Adobe Professional.
In the PDF, the user clicks in a Document Signature field to sign the document. It takes a VERY long time for this signature process to complete.
is there a trick I am missing? Is the slowness due to the way the digital ID was created?

Unfortunately, I cannot forward the form as it contains client data.
I have tested signing another PDF I've created with 2 fields using the same the digital ID's, and the process completed quickly.
Perhaps the problem lies with the size of my form which has 20 pages with 50 fields (on average) per page.
When signing the document, the signature details appear, the "saving file" temporary status bar appears and THEN the hourglass kicks in and takes 5 minutes before control is returned. Is there validation particular to the signing process I can disable? Alternatively, can I specify which pages are certified instead of the entire document?

Problem with digital signature of documents

I have a requirement to upload documents and his respected fingerprint signed (SHA1WithRSA).
To achive this I am using the functions modules:
SSF_KRN_DIGEST
SSF_KRN_SIGN_BY_AS
but I can´t make it work.
I also ask for the .pem file used to generate the PSE that I'm using to sign documents.
With this pem file I execute in openSSL this following command:
#Creates Message Digest of document.txt, and the sign it with MyKey.pem
dgst -sha1 -sign MyKey.pem -out document.sign document.txt
AND THIS WORKS! Now, with this succesfull case I try to track down the problem with the FM that I'm using, and I detected that SSF_KRN_DIGEST is given me a diferent result than openssl (so I forget for sign the document for a while...).
This are the HEX value for OpenSSL (this is the one that works):
30
21
30
09
06
05
2B
0E
03
02
1A
05
00
04
14
AC
37
25
AC
AD
34
E2
F8
B9
21
B3
15
DD
20
0D
71
5B
FD
EE
EB
And this is the HEX value of the result of FM SSF_KRN_DIGEST:
30
40
06
09
2A
86
48
86
F7
0D
01
07
05
A0
33
30
31
02
01
00
30
09
06
05
2B
0E
03
02
1A
05
00
30
0B
06
09
2A
86
48
86
F7
0D
01
07
01
04
14
AC
37
25
AC
AD
34
E2
F8
B9
21
B3
15
DD
20
0D
71
5B
FD
EE
EB
As you can see, both files do countain the digest, but the metadata and padding is different. As far as I know, it should respect the ASN.1 structure, but I can figure out whats wrong with the SSF_KRN_DIGEST call.
This is my code:
* Creamos el message diggest del archivo
CALL FUNCTION 'SSF_KRN_DIGEST'
   EXPORTING
     b_detached                         = 'X'
     ostr_input_data_l                  = lv_bin_data_len
     str_hashalg                        = 'SHA1'
IMPORTING
    ostr_digested_data_l               = lv_digested_len
*   CRC                                =
   TABLES
     ostr_input_data                    = lt_bin_data
     ostr_digested_data                 = lt_digested_data
EXCEPTIONS
    ssf_krn_error                      = 1
    ssf_krn_noop                       = 2
    ssf_krn_nomemory                   = 3
    ssf_krn_opinv                      = 4
    ssf_krn_nossflib                   = 5
    ssf_krn_input_data_error           = 6
    ssf_krn_invalid_par                = 7
    ssf_krn_invalid_parlen             = 8
    ssf_fb_input_parameter_error       = 9
    OTHERS                             = 10.
Where lt_bin_data contains the document, uploaded in binary mode.
Thanks in advance.
regards.

Martin, as you said, the problem was the PKCS#7 format.
In a communication problem, I was told that the application works with that format, whereas in reality is working with PKCS#1 - V1.5
I just have to search for a FM that support that format, like SSFW_KRN_SIGN.
This FM calculates the MD, and sign it, so it was easier than I originally thought.
This is the FM call that I'm using, just in case someone needs the code:
* Leemos los parametros definidos en la SSFA
CALL FUNCTION 'SSF_GET_PARAMETER'
   EXPORTING
     application             = 'INTBAN'
   IMPORTING
     str_profileid           = lv_profileid
     str_profile             = lv_str_profile
   EXCEPTIONS
     ssf_parameter_not_found = 1
     OTHERS                  = 2.
*Cargamos la tabla con el encargado de firmar
lw_signer-id = lv_profileid.
lw_signer-profile = lv_str_profile.
INSERT lw_signer INTO TABLE lt_signer.
*Calculamos MD del documento (SHA1), y firmamos
CALL FUNCTION 'SSFW_KRN_SIGN'
   EXPORTING
     str_format                   = 'PKCS1-V1.5'
     str_hashalg                  = 'SHA1'
     ostr_input_data              = lv_xstring_data_to_sign
   IMPORTING
     ostr_signed_data             = lv_xstring_signed_data
   TABLES
     signer                       = lt_signer
   EXCEPTIONS
     ssf_krn_error                = 1
     ssf_krn_noop                 = 2
     ssf_krn_nomemory             = 3
     ssf_krn_opinv                = 4
     ssf_krn_nossflib             = 5
     ssf_krn_signer_list_error    = 6
     ssf_krn_input_data_error     = 7
     ssf_krn_invalid_par          = 8
     ssf_krn_invalid_parlen       = 9
     ssf_fb_input_parameter_error = 10
     OTHERS                       = 11.
Where lv_xstring_data_to_sign is just a xstring with the document that I have to sign.
Regards!
German Guzelj

Multiple digital signatures in one file

I have a client who wants me to combine 4 different forms into one--then--require a digital signature by the same person after each independent form. So that would be 4 digital signatures total. And all identical. I'm using a different name per each field so there's no conflict.
It appears to work fine until I have it submit dynamically with a PHP script via email inbox.
When I open the PDF (having crunched the info back in from an FDF) the data is there EXCEPT the digital signatures.
Can someone point me to a tutorial?
Best regards,
Mare

Hi Mare,
You cannot merge files and expect that the digital signatures will be preserved. When you sign a file you are signing all of the bytes in that file, and only that file. Once you combine files you are creating a new unsigned file. If someone were to sign the new file they are signing all of the bytes in the new file, not just some of the bytes. There is no "page level" signing in PDF files, only whole file signing.
You can however put the signed files into a Portfolio file. A Portfolio keeps the files separate. Think of a Portfolio like a file cabinet in the physical world. Just because you put different files into the file cabinet drawer, they don't merge.
Steve

How can I save PDF document after Digital signature ?

I am using adobe reader and after signing the document (Digital signature) I can not save the document.

What is your operating system? What is your Reader version?
I probably won't have an answer for you, but the information may help somebody else who might.

"Save As" requested instead of "Save" after digital signature of my PDF

Hi all,
I use Adobe Reader XI.
I have a PDF file configured with a set of fields to be filled in.
One of these fields is a digital signature field.
Everyting is working fine: I can fill the fields and sign the document with my ID card, as you can see below :
The problem I have is that when I sign my document with my digital signature, Adobe request a "Save As". I would like to know if there is a way to only use a "Save" ?
That requirement is very important since we will deploy the solution to more than 5000 users in an environment which is integrated with other tools, and for the whole stuff to work, the users can't change the file name nor file path... In that scenario, you will understand that proposing a "Save As" by default is not the good way to go.
Ciould you please tell me if a solution exists for this ?
Thanks already
Benoît

Never mind, I found the answer.
A matter of setting the Firefox options so that PDF files open in Reader or whatnot rather than prompt to save.

Want insertion of Digital Signature not to require a save

I have an issue that I would appreciate someone's help on. I have been with Adobe Tech Support via their portal. Yet I have not been able to establish whether what I want to accomplish is doable.
What I have is a document that actually consists of several documents, which in aggregate comprises our application for persons wanting to drive for us. For the sake of this scenario please understand that the document is not to be broken up into multiple files. It is created as a single document to facilitate the management of the numerous applicants by in-house staff.
Anyway - this form has multiple digital signatures. The department head insists on this as each section of this document has information to be attested to as original and accurate. However, we find that only the first digital signature is used to certify the document, and any additional serve only in a "confirming" capacity.
So we have this document with multiple digital signatures, the first of which certifies the document and the remaining as "confirmation". And all of these digital signature fields are set as "required" in their properties. The form is developed and presented for testing. So we enter just one of the several digital signatures and attempt to save the file. What we expected to happen was the pop-up of a dialogue to point out that all of the required digital signature fields were not completed. But no such warning arises, and this circumstance "raises an eyebrow" or two within the firm, who expect this edit to appear.
Based on recommendations from Adobe support I go out to the developers site and research scripting. After several hours I come away with a script that will indeed spawn a message when any digital signature is missing. However, another problem arises. After closing out the dialogue box and inserting the first of several missing digital signatures I am immediately required to save the file. The save works and here we have the form with several digital signatures still not signed. This allows the user to forward on the form to us, at which time the file will be reviewed and returned to the user for further completion. And in the event that only one of several missing signatures is entered, and the file again saved and forwarded, this scenario has the potential of being repeated several times.
Is there any way through scripting for the insertion of the digital signature not to spawn a save of the document? Thanks!

Is there any isight as to how this is done?
I am currently opening a file from Teamcenter engineering, however if I try to save the file it complains there is another copy open elsewhere (which isn't true). I have to export the file first, save it and then check it back in. It seems to be the only area that behaves like this, as I am able to markup the document add pages,etc and save the document just fine.
If I could remove the save as function and just use "Save" I think that this would help.
Appreciate any/all replies!
Regards,
Sean.

Export Page as PDF after Digital Signature

Hi there!
I'm looking for a script that will export the page that is being signed (Page 2 of an 85 page document) after it is digitally signed.
Thanks!

Oh really? That's so odd! I can set up a button that extracts the page with an inputted signature, but I suppose that since that will be digitally signed, it will not work that way?
What I'm thinking is that when I digitally sign the document, it saves a new version of it that IS signed. I'm hoping to do that for just that exact page and not the entire document.

Digital signatures and view document througt URL

Hello together,
We use status document and digital signatures workflow and we canu2019t use URL link to documents which have been approved. In browseru2019s window I see digital signatures information and error :u201DHTTP 404 the web page cannot be foundu201D.
In transaction SOLAR01, SOLAR02 when, I display approved document, at first I see the windows with digital signatures information and then, after push enter - required document.
If document in status u201Cin progressu201D we donu2019t have problem.
Could you help me to resolve this problem or disable windows with signatures information?

Hello Francesco,
I want to generate a digital signature (PKCS#7,XML) using SAP SSF API as explained in
http://help.sap.com/saphelp_nw04/helpdata/en/4f/65c3b32107964996a56e4165077e24/content.htm and in Amol Joshi's reply in
Digital Signatures and Document Encryption api
so my question is From which PI/XI version and its SPS this SAP SSF LIBRARY is supported ?
Kind Regards,
Kubra fatima.

Multiply digital signature in document - prevent save after each

Similar Messages

Maybe you are looking for