Digital Signature or Certification

I have created a digital signature from an image to use when certifying documents. I want to use the image as well as some of the Text options withing Adobe Acrobat Pro (9). However, I need to be able to reduce the size of the text that I include in the certification. Specifically I want to use the "Date" and "Reason" fields within the signature. Is there a way to reduce the size of the preset fields?

Hi Todd,
The short answer is no.
As an aside, the signature field is a special use text field and what you see is just a representation of the actual signature (which is a blob of hex encoded data in the PDF file that the end-user never sees). This field has two layers, a background and a foreground. The background is partially controlled by the Logo checkbox on the "Configure Signature Appearance" dialog. You can also replace the PDF trefoil logo with a custom logo, but that's a different subject.
The foreground layer itself is divided in half, there is a graphics portion on the left and a text potion on the right. I understand what you are trying to do, that is only include two pieces of text without the size changing. Unfortunately, Acrobat (or Reader) automatically controls the text size to to keep the presentation proportional to the size of the field. If you include a bunch of items the text gets smaller so all if it will fit, with just a few items the text gets larger to fill the space. There is no method by which you can adjust the size of the text. You can play with different fonts and you will get different sizes and appearances, but for the most part this isn't going to make enough of a change to get the effect you are striving for.
Steve

Similar Messages

WDJ Adobe digital Signatures

Hello SDN,
I have to implement Digital signatures in my Webdynpro interactive forms. In sdn I found one example related to online Interactive form security but for offline I couldnt find.
In offline scenario, a user will send pdf form to customer or employee etc to fill the form and send it back.
1) Here how a receiver will know that he got the form, from an authorized person?
2) Once the form is filled and send it back, how receiver can validate whether the filled form came from an authorized person?
3) Also how exactly I can use digital signatures? what are the technical requirements for implementing digital signatures?(SSL is mandatory?)
Can some one guide me on this?
Appreciate your help.
With regards,
Ravi

Hi Ravi,
Digital signatures can also be created and verified as of Adobe Reader 5.1. Users can use the Adobe Acrobat Reader to display and print files in PDF format, whose content and appearance correspond to the paper version, on a cross-platform basis. The prerequisites for this are the use of the new Adobe Document Server for Reader Extensions and the replacement of SmartForms by Adobe Acrobat (this is still in development). SSF is not used.
Adobe Document Server for Reader Extensions assign additional usage rights to electronic forms that were created with Adobe Acrobat 5.0 and Adobe Form Designer 5.0. Digital signatures are a type of usage right.
Adobe Acrobat Reader 5.1 can be downloaded free-of-charge from Adobe's Web site, and processes the usage rights that were embedded in PDF forms by the Adobe Document Server for Reader Extensions.
for SSL service go through:[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/40cacc80-c1fc-2a10-f8b5-9e33b1829552]
for ADS (adobe document services) chk it out;[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50fd998b-494f-2b10-c2ab-e3513a857f62]
Digital Signatures and Certification in Forms:
[http://help.sap.com/saphelp_nw04s/helpdata/en/de/eda54dd9194cbcbb62bffaaebfa41d/frameset.htm]
If U have to implement digital certificates, from where I can get these certificates? Do U have to create on my own or need to buy from some party?
chk it out;https://www.bconline.gov.bc.ca/pdf/DigiCertFAQ.pdf
On-demand digital certificates for Adobe AIR applications:
[http://www.net-security.org/secworld.php?id=6628]
Regards,
Khushboo

Digital signature related

Hi,
Have some of the doubts related to digital signatures in Interactive Forms.
1. Can we use digital signatures from third part / external certification agency (CA) such as -Entrust ,while developing Interactive forms in SAP?
2. How signatures can be stored / retrieved from form? ( e.g. Form is developed using WD ABAP)
3. If yes, can anybody provide the steps / information on how above points can be achieved?
Regards
Akshay

Hi Akshay,
There is a eLearning class on securing adobe forms, [Securing Online Interactive Forms by Adobe (Session 8)|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/media/uuid/40cacc80-c1fc-2a10-f8b5-9e33b1829552]. This is done in Java Web Dynpro, but it might give some insight to what you are looking for.
Try these links too...
[Digital Signatures and Certification in Forms|http://help.sap.com/saphelp_nw04s/helpdata/en/18/ecb69017ad4765855425b97f666470/frameset.htm]
[Securing SAP Interactive Forms software by Adobe|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b08aaa7b-b2f3-2a10-5591-f472a273b90a]
Hope this helps...
Cheers,
Kevin

What is the certification authority, the third party that can confirm the digital signature?

I created a nice electronic signature, that I now regularly use and add to every document. I was told that a signature needs to be issued by a verification authority, a third party that is able to verify the signature, certificate. I created a free certificate at CAcert.org and tried to combine it with the adobe signature certificate file, but it doesnt support .cer and .crt files. Is the Adobe the certification authority in this case since i created signature in the Adobe software? Its not a big deal, I just want everything to be correct since I use the signature in official documents now (instead of scanning a signed document) ... Thanks for any info, ideas or help.
Jacob

Each Digital Certificate has a pair of private and public keys used for encryption/decryption. The private key belongs to the certificate owner and should be kept secret. It is protected by a password. The public key can be used by anyone. Digital certificates come in two flavors: one that contains both private and public key and one that contains only public key.
When you create a digital signature the signing process uses the private key to encrypt the signed content digest and the public key is used to decrypt it. So, only you can encrypt signed content with your certificate that has both private and private keys and anyone can decrypt it to validate the signature using certificate that has only public key. Usually, this certificate with the public key only is embedded in the digital signature, so that anyone can use it for decryption.
The .cer certificate contains only public key. Certificates with both private and public keys usually have extensions .pfx or .p12. You need one of those to sign.
CAcert.org issues only public key certificates. so you cannot use its certificates for digital signing.
Adobe is not a general purpose certification authority. It issues some certificates for internal use only.
Acrobat has a feature that allows you to create so-called self-signed certificates with both private and public keys but these certificates can be used only in a limited way. They do not provide the means to authenticate the real certificate owner nor revoke a certificate if it is stolen.
Generally, a digital signature asserts three main features:
1. Document integrity (document has not been changes since it had been signed),
2. Authentication (the signer is indeed what the certificate says)
3. Non-repudiation (the signature author cannot deny that he signed it: this is achieved via certificate revocation mechanism).
A self-signed certificate (of the type that Acrobat produces) can be used only for #1. It cannot be used for ##2 and 3. The latter two come only when a certificate (with private key) is issued by a reputable Certificate Authority which is trusted (like VeriSign, Symantec, etc.).

Digital signatures with different versions of Reader

I have created a form which requires a digital signature for approval. Typically, an employee will complete the form in Reader and forward it to a supervisor for approval. The supervisor needs to sign it digitally and forward it to me.
The issue we are having is with those employees who are completing the form in Reader and the supervisor (or someone thereafter) has a more updated version of Reader and cannot sign the document. What can we do to stop this from happening? There is no practical way to keep everyone on the same version of Reader. We will have many more forms which require a signature, and we need this issue resolved. (I am using Adobe Acrobat 9 Pro to create the forms.)
Also, is there a way to verify the digital signature without using a third-party source? At this point, we know anyone can create a digital signature using someone's hand-written signature they found on another paper and we would like to prevent this from happening. We need to validate the person who used the digital signature is really that person.
Any help is appreciated! Thank you!

If you are creating your forms in Acrobat 9 Pro. and then Reader-enabling them for digital signatures, then recipients of the form will need to use at least version 8 of the Adobe Reader. Also, you'll need to do a few things during the authoring stage of your form, if your form changes by role (i.e., additional data is entered, annotations, or multiple signatures). Mainly you'll need to use a certification sig. for the first signature and set permitted changes after certifying.
You can find a lot more detail on best practices on developing forms for multiple signatures in the Digital Signature User Guide at:
http://www.adobe.com/devnet/acrobat/pdfs/acrobat_digsig_userguide_90.pdf
The guide also explains how to validate documents (authenticity validation and document integrity validation).

Digital Signatures - Enterprise

Hello,
My company owns 55 licenses of Adobe Acrobat Standard for Windows version 9.4.5. I want to be able to have all of my employees digitally sign documents. I figured out the process thanks to online documentation. The cert is self-signed so it comes up with a warning stating the the "signature validity is UNKNOWN". I assume this is due to the self-cert process.
A couple questions
1) Is my assessment correct? Would getting a third party certification avoid this popup?
2) If so, what are the steps I need to do to get a certification from a third party like GoDaddy and allow all of my employees to digitally sign their PDF files?
Thanks,
Eric Fleet

Have a look at this it might help you?
http://tv.adobe.com/watch/acrobat-x/using-digital-signatures-in-a-pdf/
I would say that you need a certificate........look at the whole video there are bits at the end.....

Xfa Form, Digital Signatures, file attachments and Reader 9

Hi,
In reader 8 and previous, when i wanted to have a form that could be signed, passed to the next persons, added attachement signed, repeat, while maintaining the signatures valid, i could.
Since we updated to reader 9.12 all previously signed documents appear with invalid signatures and if i try to attach a file, the add button just isn't there.
If i follow he following steps:
Server side:
- Create PDF from xdp + xml (using forms).
- Assign Form Fillin, Digital Signatures and File Attachment (using Reader Extentions)
Client side:
- Populate the Form data
- Attach files
- Certifiy
- Sign (multiple Signatures)
It works fine, but it isn't the workflow i had in previous versions.
The workflow i have here is:
Server side:
- Create PDF from xdp + xml (using forms).
- Assign Form Fillin, Digital Signatures and File Attachment (using Reader Extentions)
Client side:
- Populate the Form data
- Attach files
- add Signature (only locks a collections of form fields)
- Repeat until everyone has attached their files and signed.
The problem is that this worked fine in versions before 9 (all digital signatures here validated with the yellow exclamation mark indicating new content), but in 9 and up what i get, after validating the signatures in reader, is a information indicating that the signatures are invalid because the document is either corrupt or has been changed.
Is this a bug or has this been changed from version 8 to version 9?
I've read the changelist of reader 9 and it talks nothing about this situation or Digital Rights other than form fillin, annotations and digital signtatures (the ones we can choose in the certification wizard of Acrobat Pro).
Any idea if its possible to implement the second scenario in reader 9, or even if its possible? Is there a guide on the practices Adobe garaties will allow to validate signatures in the following years? Even if it means usings PDFA.
Thanks in advance.

One last try.
You help would really be welcome in finding out the root cause of the difference in behaviour between reader 8 and 9 in this matter (bug or change).
I have no idea what documentation to read (since i've read the launch documentation and change list documentation) about reader 9, i've contacted Adobe 3 days ago (and the answer is silence, like usuall) and have no clear thought about what to say (without taking a huge risk by giving a uninformed answer) about this issue.
Thanks.

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.

Validating digital signatures successfull on Win7 but fails on Vista/XP/W2K3

Microsoft has announced (Security Advisory 2880823: Recommendation to discontinue use of SHA-1) that
they will stop recognizing the validity of SHA-1 based certificates after 2016. Microsoft started to sign their files with digital signatures which use the stronger SHA-2 hashing algorithm. For the countersignatures (Time Stamping Authenticode Signatures)
they also use SHA-256. These certificates can be validated fine on Windows 7/8 but can't be validated on Windows Vista, Windows XP and Windows Server 2003R2. The status of certificates in the Certification Path are OK but on the older operating systems the
countersignature seem to be missing... See the forum thread
EMET 4.1 Update 1: 'The digital signature of the object did not verify.' on Vista/XP in the
Enhanced Mitigation Experience Toolkit (EMET) Support Forum for several screenshots.
Can someone explain this behavior and maybe provide a solution?
W. Spu

Hi,
It looks like it is related with this
https://technet.microsoft.com/library/security/2749655
This issue might be caused by a missing timestamp Enhanced Key Usage (EKU) extension during certificate generation and signing of Microsoft core components and software.
Microsoft is aware of an issue involving specific digital certificates that were generated by Microsoft without proper timestamp attributes. These digital certificates were later used to sign some Microsoft core components and software binaries. This
could cause compatibility issues between affected binaries and Microsoft Windows. While this is not a security issue, because the digital signature on files produced and signed by Microsoft will expire prematurely, this issue could adversely impact the ability
to properly install and uninstall affected Microsoft components and security updates.
So have you applied this update on XP\Vista\Server 2003?
http://support.microsoft.com/kb/2749655
This update will help to ensure the continued functionality of all software that was signed with a specific certificate that did not use a timestamp Enhanced Key Usage (EKU) extension. To extend their functionality, WinVerifyTrust will ignore the lack of
a timestamp EKU for these specific X.509 signatures.
Yolanda Zhu
TechNet Community Support

How to configure CoSign Electronic Digital Signatures for UCM 11g

Hi everyone,
current I am doing a UCM poc with CoSign Electronic Digital Signature for a customer, this case is that when user approve a check-in PDF document in workflow, the user can use "sign and approve" to invoke the electronic digital signature action.
since ECM 11g is based on weblogic, I configured the keystore for the weblogic as the below steps:
1) use keytool to import a keystrore file just as cosigncert.jks from the cert file which provided by the vendor CoSign.
2) Security Realms->myRealm->Providers->Credential Mapping, create a new provider using "PKI Credential Mapping Provider" and configure the storekey cosigncert.jks for this provider.
3) Security Realms->myRealm->Providers->Authentication, select DefaultIdentityAsserter and add x509
4) configure storekey for AdminServer and UCM managerServer using cosigncert.jks
5) configure SSL for AdminServer and UCM managerServer.
after finishing this steps, access the UCM console to do the approve with siginature. but it always throw "can not find the validate certification path"
does any one know which step missing?
Thanks & Regards
shifeng

Take a look at this chapter in the manual http://docs.oracle.com/cd/E23943_01/doc.1111/e10978/c03_repository.htm#CSMRC1611
(Electronic Signature is now a feature of WebCenter Content; if you are looking for a 3rd party solution for signatures, but perhaps also timestamps, check what partners can do for you)

AIP-51083: General failure creating S/MIME digital signature

I want to do a test my B2B server whether it can sent B2B with certification request, so first I config
my wallet file is ewallet.p12, not txt file, so I locate wallet location in tip.properties:
oracle.tip.adapter.b2b.WalletLocation = file:D:\\EAIB2B\\B2BServer\\ip\\config
and then in the B2B config console change the wallet password.
I find such error log as below when I sent B2B request, it expose AIP-51083: General failure creating S/MIME digital signature: java.lang.NullPointerException
Description: General failure creating S/MIME digital signature
StackTrace:
Error -: AIP-51083: General failure creating S/MIME digital signature: java.lang.NullPointerException
at oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging.sign(SmimeSecureMessaging.java:1083)
at oracle.tip.adapter.b2b.packaging.MimePackaging.createSignatureMimeBodyPart(MimePackaging.java:480)
at oracle.tip.adapter.b2b.packaging.MimePackaging.createMultipartMessage(MimePackaging.java:934)
at oracle.tip.adapter.b2b.packaging.MimePackaging.doPack(MimePackaging.java:1132)
at oracle.tip.adapter.b2b.packaging.MimePackaging.pack(MimePackaging.java:3172)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1685)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NullPointerException
at oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging.sign(SmimeSecureMessaging.java:990)
... 10 more

Hi,
Please refer -
AS2 error: IP-51083: General failure creating S/MIME digital signature
Place your wallet at default wallet location - Midtier_Home/Apache/Apache/conf/ssl.wlt/default and mention this location in your tip.properties file.
Regards,
Anuj
Edited by: Anuj Dwivedi on Jun 28, 2009 7:33 PM

What is digital signature

hi friends,
can any one give brief information about the follwing two statements,these statements are the features of ADOBE.
Activate enhanced functions such as comments
Digital signatures and form certification

Hi,
Activate enhanced functions such as comments
So called usage rights can be apllied to a PDF form to enable additional functionality in the free Reader. The example here is a commenting menu.
Digital signatures
Is a client side digital signature to sign the content of a document.
form certification
Proof of origin of a document. A PDF form is certified on the sever after creation. If you trust the person/organization that certified the document you can be sure that the PDF document does not misbehave.
Hope this helps,
Juergen

Basic Doubts in Digital Signatures ES

1) Revocation Checking : i read that the certifications will be checked(to see whether it has been cancelled) by checking the CRLs list. Where can i find this list?
2) What is the concept behind Long Term Validity in Digital Signatures ES.
Please help me in understanding Digital Signatures ES.

Revocation Checking : i read that the certifications will be checked(to see whether it has been cancelled) by checking the CRLs list. Where can i find this list?
ANSWER: The CRL typically resides on a server somewhere, and is accessible with an http URL. The URL is specified within the digital certificate itself. From an Acrobat point of view, when a CRL is acceesed during a revocation check, it may be cached on the client side. The cached CRLs are stored at:
C:\Documents and Settings\enteruserproflehere\Application Data\Adobe\Acrobat\9.0\Security\CRLCache
What is the concept behind Long Term Validity in Digital Signatures ES.
Long Term validation has to do with how are signatures validated many years down the road... When certificates expire (typically the validity period for a certificate is 1 year) the status of the signature can change. It does not mean that the signature is invalid, it just means that based on the current time, the certificate has expired and therefore this is reflected in the signature status. If the signature is validated in the future using "The time at which the signature was created" then it will report a Valid different status (assuming the document has not been tampered with.
The "time" used to validate signatures is a Preference setting in Acrobat and Reader (Edit > Preferences... > Security > Advanced Preferences... > Verification)
Regards
Steve

Message level security: difference digital signature and certificate

Hi everybody,
could anybody please explain the difference between <b>digital signature</b> and <b>certificate</b>?
Thans
Regards Mario

Mario,
A digital signature is an electronic signature that can be used to authenticate the identity of the sender of a message or the signer of a document, and possibly to ensure that the original content of the message or document that has been sent is unchanged. Digital signatures are easily transportable, cannot be imitated by someone else, and can be automatically time-stamped. The ability to ensure that the original signed message arrived means that the sender cannot easily repudiate it later.
A digital signature can be used with any kind of message, whether it is encrypted or not, simply so that the receiver can be sure of the sender's identity and that the message arrived intact. A digital certificate contains the digital signature of the certificate-issuing authority so that anyone can verify that the certificate is real.
where as
A digital certificate is an electronic "credit card" that establishes your credentials when doing business or other transactions on the Web. It is issued by a certification authority (CA). It contains your name, a serial number, expiration dates, a copy of the certificate holder's public key (used for encrypting messages and digital signatures), and the digital signature of the certificate-issuing authority so that a recipient can verify that the certificate is real. Some digital certificates conform to a standard, X.509. Digital certificates can be kept in registries so that authenticating users can look up other users' public keys.
hope it helps u.
--Archana

Failed to Verify License File Digital Signature

We are trying test our license file with our add-on identifier as provided by SAP. We keep getting a different error each time. Now we are getting "failed to verify license file digital signature" After we did the name substitutions in our license file. How do we fix this?

Hi,
I am sorry, but this is the forum around Solution Certification - not about general SDK questions or issues.
Please use the "regular" Forum (SAP Business One SDK)!
Thanks
PS: You must never modify the license file!

Digital Signature or Certification

Similar Messages

Maybe you are looking for