Signature behavior

What exactly is a signature? I know how to use it, but I am interested in more detail.
Is it a separate entity from the email body? Is it just pasted into the body?
Why are there problems sometimes, such as in an older version of mail, if there was a picture attached, it had to be in a certain location in the email or else there was a problem. (I don't remember that exactly anymore). Is there still a problem with signatures and mail?
Does the placement of the signature set mail up for problems? (e.g., at the end of the quoted text or above it)
Answers to these questions and any other issues would be appreciated.

This is an informative article from macosxhints. It talks about making signatures color, but if you read all the related posts they provide useful insight.
http://www.macosxhints.com/article.php?story=20060130112053611&lsrc=osxh

Similar Messages

Strange signature behavior

My question concerns changing my signature. I have several signatures set up for different situations. If I begin a brand-new message, I can decide to change which signature I'm using at any point in the creation of that message.
However, if I'm replying to a message I've received, I can only change my signature before I begin typing my response. If I try to change my signature after I've begun typing, the drop-down list says it's using the signature I've selected, but the signature itself does not change, and the recipient does not see the change.
Is this a bug, or am I doing something wrong?
Thanks!

Never mind. I discovered that this was linked to the way I was receiving messages from an online group. I changed the settings there, and the problem was solved.

Excel 2013 crash - related to digital signature?

This is a cross-posting of a thread originally started in Microsoft Answers (Office- Excel) forum, advised to post in this forum by MS support engineer Mohan Suryanarayan (link to other forum: here).
I have a VB macro in file A (which otherwise contains only several Excel Tables with named ranges). My digital signature (for signing code) is attached to file A.
As the macro executes, the Open file dialog is called up so that the User can select a secondary file to open (file B or C).
Files B and C contain several sheets with formulas and Excel Tables, and also their own extensive VB macros. My digital signature is also attached to files B & C.
The remainder of the macro in file A simply executes an update of the Excel Tables in the secondary file, before saving & closing it.
I have been finding that during execution of the file A macro, Excel crashes and closes all open Excel files.
If I remove the digital signature from the secondary files then the macro in file A executes with no problem.
The macro was written in Excel 2007 and on a different laptop, with different digital signature, and used to have no problem at all. When a new laptop was purchased a new digital signature was obtained and placed into all of the files.
Execution of file A is a critical process - I need help with stopping the crash, while maintaining a digital signature in the secondary files (so that their own macros can execute).
Event Viewer error shows the following:
Faulting application name: EXCEL.EXE, version: 15.0.4667.1000, time stamp: 0x543d366c
Faulting module name: mso.dll, version: 0.0.0.0, time stamp: 0x5447696f
Exception code: 0xc0000602
Fault offset: 0x011aafdd
Faulting process id: 0x2d58
Faulting application start time: 0x01d01e17eafcd0bb
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\EXCEL.EXE
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
JL Latham replied:
Tom, all I can give you is relatively non-information. I haven't experienced that type of behavior even in Excel 2013 with digitally signed macros in multiple workbooks. But my digital signature is a commercial one from DigiCert, not
self-cert. I'm not even sure what piece of Excel or Office processes the digital signature (that is, whether it is mso.dll or not). But your whole process has more moving parts than most of mine involving multiple workbooks do - I quite often turn
off .EnableEvents when doing things like that just so event driven macros in the other workbook(s) do not execute.
Do the macros in the 'B files' have to execute during all of this processing in file A? If not, have you tried turning interrupts off:
Application.EnableEvents = False
before starting to work with the B-files? Maybe something in them, such as a Worksheet_Change() or other event triggered process is messing things up?
If you do use Application.EnableEvents=False, remember that you MUST re-enable that later in the code with Application.EnableEvents=True to get responses to things like button clicks, changes in a worksheet or other event driven processes
to run 'normally' again.
Have you looked at this discussion:
http://answers.microsoft.com/en-us/office/forum/office_2013_release-excel/excel-2013-crashing-immediately-when-attempting-to/ea2ab100-5525-4a0d-a3cf-6977319f954f
Sounds very similar to yours - original signature created in 2007, and crashing in 2013. Some suggestions were made, but whether they fixed the issue or not is unknown: OP never came back and said "fixed it" or "didn't fix it".
I replied:
In answer, the secondary B files don't execute any part of their macros during the A file process, and I hadn't included an EnableEvents = False within the file A code. However, I have just tried it to check if it made any difference and unfortunately it didn't.
I had read the thread you gave a link to before posting, and also the sub threads given within that one, but didn't see anything I thought of immediate parallel other than an Excel 2013 crash.
The way I read the linked thread was that a User added a signature in Excel 2007 and when they tried to open the file Excel (2007?) crashes, although other people using Excel 2013 can open it (not clear whether it means others can open the one with
the 2007 signature or without it).
Anyway, the differences in my situation are that:
(1) my B-files were originally created in Excel 2007 on a different laptop to current and had their own signature attached. I maintain a 'stock' of B-file versions, some of which have the old signature and some the new. If I run the A-file macro
on one of the B-files with the old signature then it executes ok;
(2) I am able to open the B-files ok, no matter whether the signature in them derives from the old laptop with Excel 2007 or the new laptop with Excel 2013;
(3) the macros within the B-files execute ok (this includes any versions of the B-files which still have an old signature attached, by removing the old signature and replacing with the new and executing on the new laptop);
(4) the offending operation which triggers the crash (when the B-files have the new signature attached) is a Resize of the Excel Tables within the B-file. I understand that I may eventually have to find a workaround for this operation but initially
I want to sort out the signature issue (I'm reasonably sure the signature issue is not a red herring where the Resize is the 'real' problem).
Regards, Tom

Hi,
According to your description, this issue occurred with some particular files that stored in SharePoint site. Did the user download the file to local disk to print?
Based on the event log >>Faulting module name: EXCEL.EXE<<, it does not show the root Faulting module. Thus, please try to follow this KB to do general troubleshooting:
https://support.microsoft.com/en-us/kb/2758592
Then, if you have used "printer status application", please go to Device settings -> Installable options -> Printer Status notification and select disable.
If this issue still exists, we may need to collect the App crash dump file:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
You can try to analyze dump by yourself if you would like to：
How to analyze app crash dump file:
http://blogs.technet.com/b/askperf/archive/2007/05/29/basic-debugging-of-an-application-crash.aspx
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

JSR 172: error while invoking methods of same signature

Hi
I am facing a peculiar problem which is not making sense to me. This is what I have done:
1. Written a simple web service that has two methods: sayHello and sayHellToMe. Both these methods have same signatures. They do not take in any parameter and return a string.
2. Deployed this web service (document/literal) type on Axis 1.2
3. Generated the stub classes from the wsdl file using Sun Wireless Toolkit's Stub Generator
4. I have now written a MIDlet that uses this stub class to invoke both the methods one after the other.
I enabled SOAPMonitor on Axis and saw the SOAP Request and SOAP Response messages. I observed the following:
1. In the first method: sayHello - everything works fine (with a few tweaks in the Stub class)
2. However, while invoking the second method sayHelloToMe, the SOAP Body tag in the SOAP Request does not contain any method name. I checked out the Stub class, the qnames and the types are all correct..
I also realized that this behavior is seen only when I have methods with the same signature in the web service. Any idea why this might be happening? It seems like a very weird problem.
Any help in this regard will be greatly appreciated.
Thanks,
Arati

The 'numeric or value error' is one we have seen many times. The problem has been identified and fixed. Refer to this thread for more information.
Issue with DB Adapter - ORABPEL-11811

JSR 172: error while invoking methods with the same signature

Hi
I am facing a peculiar problem which is not making sense to me. This is what I have done:
1. Written a simple web service that has two methods: sayHello and sayHellToMe. Both these methods have same signatures. They do not take in any parameter and return a string.
2. Deployed this web service (document/literal) type on Axis 1.2
3. Generated the stub classes from the wsdl file using Sun Wireless Toolkit's Stub Generator
4. I have now written a MIDlet that uses this stub class to invoke both the methods one after the other.
I enabled SOAPMonitor on Axis and saw the SOAP Request and SOAP Response messages. I observed the following:
1. In the first method: sayHello - everything works fine (with a few tweaks in the Stub class)
2. However, while invoking the second method sayHelloToMe, the SOAP Body tag in the SOAP Request does not contain any method name. I checked out the Stub class, the qnames and the types are all correct..
I also realized that this behavior is seen only when I have methods with the same signature in the web service. Any idea why this might be happening? It seems like a very weird problem.
Any help in this regard will be greatly appreciated.
Thanks,
Arati

Hi, I'm closing this thread and opening the same in another as the content got pasted in reader un friendly format and i'm unable to change the format.
Thanks,
Ravi.

The extension does not contain a valid signature

hey guys, newbie on deck!
So, after installing CS6 I ran the Adobe Update Manger. During the update the Adobe Extension Manager (AEM) fired off and began updating as well. One error I saw was:
The extension 'Adobe_Flash_Professional_Toolkit_for_CreateJS' does not contain a valid signature. The extension will not be installed.
I'm not sure what this is or what it does but I would like to:
Understand the Adobe ecosystem and
Clear any problems.
Here's what I do know:
The Mac I have is 2 days old and probably in the best shape of its life.
I installed CS6 fresh from a DVD.
Ran the Adobe Update Manager the next day (today).
I don't intend to use Flash.
If anyone can expain common causes for this behavior and a fix I would greatly appreciate it.
Thanks in advance,
TT

Hi JesusPresley,
The root cause is the updater updated Adobe Flash, which tried to install the extension above by Extension Manager in the installation. However, this extension was NOT signed with the updated Adobe certificate, so the extension installation will be rejected by Extension Manager. That is what you got. We have sent this issue to Flash team.
If you don't use Flash, you can manually edit C:\Program Files\Adobe\Adobe Flash CS6\XManConfig.xml, and remove the line <Data key="SupportedInSuite">CS6</Data>. Thanks.
Xiaoyi

Issue with validation of signature

Hello,
I am facing a problem in producing a correct signature and I hope someone can help me understand the root of the problem. Most of us are familiar with the Java (Sun) examples of GenDetached, GenEnveloped, GenEnveloping, and Validate code samples. The code below is a small variation of the GenDetached:
public class GenerateDetachedWithManifest {
public static void main(String[] args) throws Exception {
    // First, create a DOM XMLSignatureFactory that will be used to
    // generate the XMLSignature and marshal it to DOM.
    String providerName = System.getProperty("jsr105Provider",
        "org.jcp.xml.dsig.internal.dom.XMLDSigRI");
    XMLSignatureFactory fac = XMLSignatureFactory.getInstance("DOM",
        (Provider) Class.forName(providerName).newInstance());
    // Create a Reference to an external URI that will be digested
    // using the SHA1 digest algorithm
    Reference ref = fac.newReference("http://www.w3.org/TR/xml-stylesheet", fac
        .newDigestMethod(DigestMethod.SHA1, null));
    Reference xref = fac.newReference("#object", fac.newDigestMethod(
        DigestMethod.SHA1, null), null, "http://www.w3.org/2000/09/xmldsig#Object", null);
    Manifest manifest = fac.newManifest(Collections.singletonList(ref));
    List<XMLObject> objs = new ArrayList<XMLObject>();
    objs.add(fac.newXMLObject(Collections.singletonList(manifest), "object", null, null));
    // Create the SignedInfo
    SignedInfo si = fac.newSignedInfo(fac.newCanonicalizationMethod(
        CanonicalizationMethod.INCLUSIVE,
        (C14NMethodParameterSpec) null), fac.newSignatureMethod(
        SignatureMethod.DSA_SHA1, null), Collections.singletonList(xref));
    // Create a DSA KeyPair
    KeyPairGenerator kpg = KeyPairGenerator.getInstance("DSA");
    kpg.initialize(512);
    KeyPair kp = kpg.generateKeyPair();
    // Create a KeyValue containing the DSA PublicKey that was generated
    KeyInfoFactory kif = fac.getKeyInfoFactory();
    KeyValue kv = kif.newKeyValue(kp.getPublic());
    // Create a KeyInfo and add the KeyValue to it
    KeyInfo ki = kif.newKeyInfo(Collections.singletonList(kv));
    // Create the XMLSignature (but don't sign it yet)
    XMLSignature signature = fac.newXMLSignature(si, ki, objs, "SignatureIdValue", null);
    // Create the Document that will hold the resulting XMLSignature
    DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
    dbf.setNamespaceAware(true); // must be set
    Document doc = dbf.newDocumentBuilder().newDocument();
    // Create a DOMSignContext and set the signing Key to the DSA
    // PrivateKey and specify where the XMLSignature should be inserted
    // in the target document (in this case, the document root)
    DOMSignContext signContext = new DOMSignContext(kp.getPrivate(), doc);
    // Marshal, generate (and sign) the detached XMLSignature. The DOM
    // Document will contain the XML Signature if this method returns
    // successfully.
    signature.sign(signContext);
    // output the resulting document
    OutputStream os;
    if (args.length > 0) {
      os = new FileOutputStream(args[0]);
    } else {
      os = System.out;
    TransformerFactory tf = TransformerFactory.newInstance();
    Transformer trans = tf.newTransformer();
    trans.transform(new DOMSource(doc), new StreamResult(os));
}If you wonder why I am doing this the answer is that I am trying to sign a format based on OPC. Anyway, the problem I have is that the output of the above program fails to validate when running the Validate sample. I don't think the issue is with the Validate program because it correctly validates output of a .NET signing application whose behavior I am trying to replicate in Java.
So the question is: why does the above code produce an incorrect signature?
Thanks,
Luis

Can you post relevant sections of the OPC standard (or a link to it) that describes the requirement? Its possible that they have written the requirements differently from the examples. Its also possible that the DSIG library in the JDK only does things in a specifc way (I'll let Sean Mullan weigh in on this part of the discussion if he's monitoring this list/thread - he's the developer from Sun who wrote the library).
Here's the wording from the W3C spec on the Object element:
+"The Object's Id is commonly referenced from a Reference in SignedInfo, or Manifest. This element is typically used for enveloping signatures where the object being signed is to be included in the signature element. The digest is calculated over the entire Object element including start and end tags."+
What you have is neither an Enveloping Signature nor Detached - but a combination of the two. So its possible that the JDK library doesn't work with Object references in this manner (although in theory is should). Based on this thread (XML dsig: Can I sign a SignatureProperty of the Signature? it appears that this theory holds up for child-elements of Object , but not for the Object element itself.
Arshad Noor
StrongAuth, Inc.

Adobe Acrobat 9 Signatures

I have set up a signature in Adobe Acrobat 9 and when you draw the box for placing your signature everything behind it is "whited" out. Is there a way to change the settings so you can see where you are placing your signature? I have to sign a lot of documents (i.e. contracts) where I have limited place to place it and I need to not cover up the wording where I placing my signature. Is there any way to do this? Any offered suggestions to solving my problem??
Thanks

Hi Amy,
I'm a bit surprised you are seeing this because it is not the default behavior. Normally, when you add a signature field to the document both the fill and border are turned off. But, since it is looks like fill is enabled what you could do is:
Select the View > Toolbars > Advanced Editing menu item
Click on the Select Object tool (it's the arrow that points to the upper left on the Advanced Editing toolbar)
Right mouse click on the signature field that is obscuring the underlying text or image
Select Properties from the pop-up menu
Select the Appearance tab on the Digital Signature Properties dialog
Click the button next to Fill Color and then select No Color from the pop-up pallet
Click the Close button on the Digital Signature Properties dialog
That should get you fixed up. I hope this helps,
Steve

Able to clear signatures in a certified document in Acrobat 9.0

Hi
While testing Acrobat 9.0 feasibility for migrating my application from Acrobat 7.0, I stumbled upon a security issue that the signatures can be cleared in a certified document (Only Form Fill in and digital signatures are allowed) by right clicking and selecting Clear
Signature. After clearing the signature, the document status still remains valid i.e. it doesn't gets invalid even if the signature is cleared. Below are the steps to reproduce the same.
1. Certify a document having couple of signature fields by selecting Certify with Visible Signature and
i "Form fill-in and digital signatures"
as the Permitted Actions after Certifying.
2. Close and re-open the document.
3. Sign a signature field.
4. Close and re-open the document. Right click on the signed signature field and select Clear Signature.
5. Save the document, close and re-open the same. The signature is cleared
and the document status is valid.
This behavior is different from Acrobat 7.0 where
A) User is unable to clear a signature in a certified document
B) Even if he somehows clears the signature, the document certification becomes invalid.
Also, if you right click on the certifying signature in Step 4 above, it also can get cleared.
This behavior of clearing the signatures in a certified document nullifies the purpose of a certified document to prevent users from changing a document. Also, the option of locking the signature during the certification process is missing in Acrobat 9.
Please let me know whether this is a bug or expected behavior.

Below is the example of difference in behavior of Acrobat 7 and 9.
In case of Acrobat 7, there was no option to clear a signature field in a "certified" document i.e. if I sign and right click on a signature field inside a certified document Acrobat 7.0, the Clear Signature option is not present.
However, if I sign the same signature field in the same PDF in Acrobat 9 and right click, Clear Signature option is available and am able to Clear the signature.

Acrobat 9,10 failing to validate digital signature while Acrobat 8 validating it.

I am facing an issue while validating a digital signature. I applied a certified signature with “Annotation, form fill-in, and digital signatures” but
when I apply Redaction “find and permanently remove” on a digitally signed document, Adobe Acrobat 9 and 10 complains that signature is Invalid But Adobe 8 is validating it. I have analyzed that Adobe Acrobat applying Redaction in append mode and original content of signature remains unchanged after Redaction.
Can someone let me know what should be the actual behavior?
Why Adobe Acrobat 9 and 10 failing to verify the signature even Adobe Acrobat keep enable Redaction which means it is allow to apply in a certified signed document with “Annotation, form fill-in, and digital signatures” option.
Prompt responses are greatly appreciated!!

When you sign, you should see where you can select the signature appearance name from a dropdown in the dialog.

Multiple Digital Signatures in Acrobat 8.1

Hello to all, I am trying to have two people place two (2) digital signatures (using the method: Advance Menu Item | Sign & Certify | Place Signatures) on a PDF document.
There are no problems placing the first signature, but when the second person adds theirs, the first signature ends up having a yellow exlamation mark over the green check mark with the statement: "The revision of the documnet was covered by this signature has not been altered; however there have been subsequent changes to the doucment.".
I must have both signatures showing "green check marks", otherwise my document can be rejected when I submit it. I have version 8.1 of Acrobat and need a solution fast as I need to submit this document tomorrow.
Thanks in advance for any help provided.

I believe this behavior was changed in Acrobat 9.

Quicktime removed re-added itunes 7, error signature

Quicktime was removed from computer.
itunes wouldn't start. re-installed updated itune 7. now itunes won't open. error report states- error signature. help! tried to restore, didn't work. either need to extract library or figure out my signature problem

now itunes won't open. error report states- error signature.
is that an "itunes has encountered a problem ..." message?
if so, let's check to see if it's currently associated with a quicktime issue.
try launching your QuickTime. does it:
(a) launch perfectly fine?
(b) fail to launch with an error message? (if so, what does it say?)
(c) exhibit other peculiar behavior? (if so, could you describe it for us?)

Digital Signature and Annotation Appearance Stream

Hello,
I've noticed that adding an annotation on a pdf without specifying an appearance stream ( AP dictionary ) for that annotation, and then signing the document,
will cause Acrobat to report that the document is Signed and all signatures are valid, but with Annotations Modified message under the signed revision in the signature panel.
So is that behavior by acrobat, while appearance stream entry is optional in annotations ?

Hello lrosenth,
I was eble to add an ink annotation with an appearance stream, and then signing the document with digital signature goes fine with no problems
( No "Annotations Modified" ) message appearing in the signature panel, but adding a freetext annotation with an appearance stream and then signing, is causing acrobat to show "At least one signature requires validating" message in the signature bar, and by validating the signature manually by pressing "Validate All" in the signature panel, the original problem appears again stating "Annotations Modified". So is freetext annotations should be considered in a different way than other annotation types ?
Thank you.

Query in Deleting the Signature using Acrobat 9.0

Hello Folks,
We have used resetForm() method before removefield() in our coding
Observed result:
Our application uses VC++,If the document has one Digital Signature using the fix(Mentioned below) we can able to delete the signature in the document but when the document has many number of Digital Signatures the fix is not working.It threws an exception
·        “NotAllowedSecurity: Security settings prevent access to this property or method”
·        The exception Id for the above exception is “0x80020009”
    Note: The behavior is wrt to Acrobat 9.0, but the code is working fine for Acrobat 7.0 and 8.0 versions.
If we try the scenario in our application, on timestamp the document with Acrobat 9.0 and then signing the document with the same acrobat 9.0 and when deleting the signature using our application again our fix is not working it throws the above exception.
The code details are given below
//Get Nth Field is done
DISPID dispidRestet;
OLECHAR *methodReset = { L"resetForm" };
hr = jso->GetIDsOfNames( IID_NULL, ( OLECHAR** )&methodReset, 1, GetUserDefaultLCID(), &dispidRestet );
if( hr != S_OK) {
*errCode = kPSWErrIDispatchGetIDOfNames;
return FALSE;
dispparam.cArgs = 1;
dispparam.rgvarg = new VARIANT[ dispparam.cArgs ];
dispparam.rgvarg[ 0 ].vt = VT_BSTR;
dispparam.rgvarg[ 0 ].bstrVal = varResult.bstrVal;
dispparam.cNamedArgs = 0;
dispparam.rgdispidNamedArgs = NULL;
hr = jso->Invoke( dispidRestet, IID_NULL, GetUserDefaultLCID(), DISPATCH_METHOD, &dispparam, NULL, NULL, NULL );
if ( hr != S_OK ) {
*errCode = kPSWErrIDispatchInvoke;
m_pAvdoc->Close(0);
ret = FALSE;
EXCEPINFO exceptionInfo;
DISPID dispid2;
OLECHAR *methodName2 = { L"removeField" };
hr = jso->GetIDsOfNames( IID_NULL, ( OLECHAR** )&methodName2, 1, GetUserDefaultLCID(), &dispid2 );
if ( hr != S_OK ) {
*errCode = kPSWErrIDispatchGetIDOfNames;
return FALSE;
dispparam.cArgs = 1;
dispparam.rgvarg = new VARIANT[ dispparam.cArgs ];
dispparam.rgvarg[ 0 ].vt = VT_BSTR;
dispparam.rgvarg[ 0 ].bstrVal = varResult.bstrVal;
dispparam.cNamedArgs = 0;
dispparam.rgdispidNamedArgs = NULL;
hr = jso->Invoke( dispid2, IID_NULL, GetUserDefaultLCID(), DISPATCH_METHOD, &dispparam, NULL, &exceptionInfo, NULL );//here hr throws the exception for multiple signed documents
if ( hr != S_OK ) {
*errCode = kPSWErrIDispatchInvoke;
m_pAvdoc->Close(0);
ret = FALSE;
//return FALSE;
else{
m_pPddoc->Save(1,strPDFFile);
m_pAvdoc->Close(true);
Plese guide us how to over come the exception
Regards,
DOCNet.

Hi Leo,
             Thanks for your reply!!!.:-)
          Both the signatures are done by me only.
          The thing is the code works fine for one signature, but it throws an exception for documents having many signatures.
          Can you guide me how to proceed further.

Adobe Reader 9, Form Fields, Digital Signature

I have already posted this in Adobe Reader forum and had no replies... probably the wrong area...
We are a software company and we are developing a simple application, as follows:
Any number of pdf documents are provided by a third party (our customer / customers). Each form contains any number of fields and a digital signature field.
Our application must fill the fields with values obtained by a back-end database
Using Adobe Reader 9, our application must display each pdf document filled in step 2, for users to sign using a Topaz tablet.
The "blank", original pdf document can be easily completed by hand and signed using the Topaz tablet - thanks to the Adobe Reader plug-in.
Also, we can quite easily fill all the doument's fields using the popular iTextSharp libraries - we extract relevant data from our back-end database, we set the field values, and we display the document in Adobe Reader 9 (note that after filling the form, we have experimented with "flattened" and "non-flattened" documents....with the same results)...
Here we start having some problems:
As soon as the "filled" document is displayed in Adobe Reader, the message "This document enables Reader capabilities that are no longer enabled in this Reader version." is displayed. And the signature field is disabled and the Topaz plug-in is never invoked.
It seems that the simple task of programmatically filling the form with data.... disable the most important feature of the form (the signature line).
Unfortunately, my knowledge of the Adobe product line is somewhat limited....
After hours of research I think I understand why (even though I find the behavior incredibly strange and restrictive). I still would like, if possible, summary and clear information on what we (and/or the provider of the pdf forms) need to do to accomplish the goal of our application.
Thanks in advance for any suggestion.
Giorgio

jmo here
In context of your description, use of Acrobat Pro to "enable" PDFs for use by Adobe Reader appears to be contrary to the Acrobat EULA (if nothing else, the "500" limit for forms).
If that's the case then I suspect your only option would be LiveCycle ES.
Back down the Forum's timeline, someone mention $50K for a seat.
But LC ES has many variations (modules if you will) so the price point may be higher.
Basically, it is expensive (although worth the $$ to the IRS and other large entities).
Worth noting are the posts in this forum that allude to Adobe's legal actions taken against those who have, it seems, violated the Acrobat EULA.
If your client(s) are associated with a corporate entity they may be exposed to legal "road hazards"; but, that's speculative, eh?
Regardless, it does sort of appear that you may be on thin ice vis-a-vis "enable" of PDFs for use by Adobe Reader.
Be well...

Signature behavior

Similar Messages

Maybe you are looking for