Digital Signature filteration (eg: cn=TEST) Javascript code

Hi
Thanks in advance....
Please find the details below :
1. When you open the PDF you will see a button. OnClicking the button the signature window displays, this window is same as the window which appears on clicking the signature field.
2. When you open this document in the Livecycle Designer you will see a JavaScript code written in the button. This code generates the window and displays all the signature deployed in the machine.
Requirement : I need to put a filter on this button, when the user clicks the button it should only displays those signatures which belongs to the particular group/profile.
Eg: cn=TEST. In this scenario it should display only those signature belonging to the TEST group/profile after clicking the button.
Basically i want to restrict only a particular group/profile to sign the document. Let me know how can i achieve this functionality..
I have attached the pdf for your reference.
Regards
Mahesh Pillay
+91-9930315761

Steve,
Thanks for your reply...
I had tried with the seed value but unfortunalty could not find the correct syntex/code for setting the seed value in my javascript code.
Appreciate if could provide me the code , since i am not an expert in javasceript and i am trying this for a very long time...
Thanks in advance...
Regards
Mahesh Pillay

Similar Messages

Digital Signature Filteration based on Profiles

Hi,
Problem : Instead of using theSignature Field and hardcoding the signature issuer profile (eg : cn=TEST), I have a javascript code written in the button which pops-up the digital signature window where all the signatures are displayed in the combo. I need to filter out only those digital signature which belongs to a particular profile.
I have attached the PDF for your reference. Please provide me the javascript code which can filter the signatures based on the profiles. Let me know if you require any more clarification for the same.
Regards
Mahesh Pillay
[email protected]

Steve,
Thanks for your reply...
I had tried with the seed value but unfortunalty could not find the correct syntex/code for setting the seed value in my javascript code.
Appreciate if could provide me the code , since i am not an expert in javasceript and i am trying this for a very long time...
Thanks in advance...
Regards
Mahesh Pillay

Digital signature properties field name via javascript

I am creating secure digital signature fields with random number names with similar prefixes. The idea is to have multiple fields available in a single regular PDF (non portfolio). So on each sheet we sign 3 fields. One field is a name, another is a date and the last is a release. This goes on every sheet and the PDF would contain up to 1500 pages. Adding a random number to the end of each field name was the only way to make this work....now I have a problem of finding the particular fields for my script to sign the sheets.
I am guessing that there must be some way to identify how many fields I have on a sheet and return the name of all the fields. If I can get the name of all the fields I can use that info to run my script to place the digital signature appearances in their correct field. My field names all begin with either 'Date', 'Sig' or 'RFC' followed by a random number to avoid duplicate fields.
So in a nut shell, how can I find the names of the fields via JavaScript?
Thanks you!

Are you able to add another prefix, specifically using hierarchical field names that include the page number? For example, on page one the fields could be named:
P1.Date[random number goes here]
P1.Sig[random number goes here]
P1.RFC[random number goes here]
You can then get all of the P1 fields like this:
var fields = getField("P1");
and then use the getArray method to get an array of the individual field references and iterate through the array.
Otherwise, you can loop through the fields and look at the page property of each to determine which ones are on which pages. You can use the getNthFieldName document method and numFields document property to do this.

Loading Invoice XML IDoc with digital signature via XI into R/3

Hi,
I received an Invoice XML IDoc with digital signature via Mail (for test purposes) and want to load it via XI into an R/3 systeme.
My idea is to load the Invoice XML IDoc file via the File Sender Adapter into XI and send it to the R/3 system via the IDoc Inbound adapter.
Due to the digital signature the file looks like this:
0 S      *H÷
   D0 @   1 0       +      0 '      *H÷
      0 0 û      etc.
When I load the file like this with the File Sender Adapter, an error message occurs in the XI Monitoring as the XML Parser cannot read the file due to the digital signatur (as expected).
Has anybody an idea how I can configure the File Sender Adapter Communication Channel to be able to load only the XML IDoc and ignore the digital Signature strings?
Thanks in advance for your support.
Alex

BTW
do use the second way you need:
Security Settings for the Sender Mail Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/27/c0524257a1b56be10000000a155106/content.htm
and
Key Storage Service
http://help.sap.com/saphelp_webas630/helpdata/DE/e9/a1dd44d2c83c43afb5ec8a4292f3e0/content.htm
apart from adapter module config
Regards,
michal

Implementing XAdES in Java XML Digital Signature API

Hi,
I've got some problems with implementing XAdES standard with Java XML Digital Signature API. Below is a code (SignatureTest1), that produces a digital signature with some XAdES tags placed in <ds:Object> tag. The signature is later validated with a Validator class. Everything works fine, until I set a XAdES namespace (SignatureTest1.xadesNS="http://uri.etsi.org/01903/v1.3.2#"). In this case validation of XAdES elements fails.
The reason of validation failture is a difference between arguments passed to a digest method when document is being signed and validated. When the document is being signed a log looks like this:
FINER: Pre-digested input:
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.DigesterOutputStream write
FINER: <SignedProperties xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="SignP"></SignedProperties>
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMReference digest
FINE: Reference object uri = #SignP
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMReference digest
FINE: Reference digesting completed,but while validating:
FINER: Pre-digested input:
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.DigesterOutputStream write
FINER: <SignedProperties xmlns="http://uri.etsi.org/01903/v1.3.2#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="SignP"></SignedProperties>
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMReference validate
FINE: Expected digest: MAQ/vctdkyVHVzoQWnOnQdeBw8g=
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMReference validate
FINE: Actual digest: D7WajkF0U5t1GnVJqj9g1IntLQg=
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMXMLSignature validate
FINE: Reference[#SignP] is valid: falseHow can I fix this?
Signer class:
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.OutputStream;
import java.security.KeyPair;
import java.security.KeyPairGenerator;
import java.util.ArrayList;
import java.util.Collections;
import java.util.Iterator;
import java.util.List;
import javax.xml.crypto.dom.DOMStructure;
import javax.xml.crypto.dsig.CanonicalizationMethod;
import javax.xml.crypto.dsig.DigestMethod;
import javax.xml.crypto.dsig.Reference;
import javax.xml.crypto.dsig.SignatureMethod;
import javax.xml.crypto.dsig.SignedInfo;
import javax.xml.crypto.dsig.Transform;
import javax.xml.crypto.dsig.XMLObject;
import javax.xml.crypto.dsig.XMLSignature;
import javax.xml.crypto.dsig.XMLSignatureFactory;
import javax.xml.crypto.dsig.dom.DOMSignContext;
import javax.xml.crypto.dsig.dom.DOMValidateContext;
import javax.xml.crypto.dsig.keyinfo.KeyInfo;
import javax.xml.crypto.dsig.keyinfo.KeyInfoFactory;
import javax.xml.crypto.dsig.keyinfo.KeyValue;
import javax.xml.crypto.dsig.spec.C14NMethodParameterSpec;
import javax.xml.crypto.dsig.spec.TransformParameterSpec;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.stream.StreamResult;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.NodeList;
import com.sun.org.apache.xml.internal.security.utils.IdResolver;
public class SignatureTest1 {
     public static String xadesNS=null;//"http://uri.etsi.org/01903/v1.3.2#";
     public static String signatureID="Sig1";
     public static String signedPropID="SignP";
     public static void main(String[] arg) {
        try{
          XMLSignatureFactory fac = XMLSignatureFactory.getInstance("DOM");
          List<Reference> refs = new ArrayList<Reference>();
          Reference ref1 = fac.newReference
              ("", fac.newDigestMethod(DigestMethod.SHA1, null),
                  Collections.singletonList
                (fac.newTransform
               (Transform.ENVELOPED, (TransformParameterSpec) null)),
               null, null);
          refs.add(ref1);
          Reference ref2 = fac.newReference("#"+signedPropID,fac.newDigestMethod(DigestMethod.SHA1,null),null,"http://uri.etsi.org/01903/v1.3.2#SignedProperties",null);
          refs.add(ref2);
          SignedInfo si = fac.newSignedInfo
              (fac.newCanonicalizationMethod
               (CanonicalizationMethod.INCLUSIVE_WITH_COMMENTS,
                (C14NMethodParameterSpec) null),
               fac.newSignatureMethod(SignatureMethod.DSA_SHA1, null),
               refs);
         KeyPairGenerator kpg = KeyPairGenerator.getInstance("DSA");
          kpg.initialize(512);
          KeyPair kp = kpg.generateKeyPair();
          KeyInfoFactory kif = fac.getKeyInfoFactory();
          KeyValue kv = kif.newKeyValue(kp.getPublic());
         KeyInfo ki = kif.newKeyInfo(Collections.singletonList(kv));
          DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
          dbf.setNamespaceAware(true);
          Document doc =
              dbf.newDocumentBuilder().parse("purchaseOrder.xml");
          DOMSignContext dsc = new DOMSignContext
              (kp.getPrivate(), doc.getDocumentElement());
          dsc.putNamespacePrefix(XMLSignature.XMLNS, "ds");
          Element QPElement = createElement(doc, "QualifyingProperties",null,xadesNS);
        QPElement.setAttributeNS(null, "Target", signatureID);
        Element SPElement = createElement(doc, "SignedProperties", null,xadesNS);
        SPElement.setAttributeNS(null, "Id", signedPropID);
        IdResolver.registerElementById(SPElement, signedPropID);
        QPElement.appendChild(SPElement);
        Element UPElement = createElement(doc, "UnsignedProperties", null,xadesNS);
        QPElement.appendChild(UPElement);
        DOMStructure qualifPropStruct = new DOMStructure(QPElement);
        List<DOMStructure> xmlObj = new ArrayList<DOMStructure>();
        xmlObj.add(qualifPropStruct);
        XMLObject object = fac.newXMLObject(xmlObj,"QualifyingInfos",null,null);
        List objects = Collections.singletonList(object);
        XMLSignature signature = fac.newXMLSignature(si, ki,objects,signatureID,null);
          signature.sign(dsc);
          OutputStream os = new FileOutputStream("signedPurchaseOrder.xml");
          TransformerFactory tf = TransformerFactory.newInstance();
          Transformer trans = tf.newTransformer();
          trans.transform(new DOMSource(doc), new StreamResult(os));
        }catch(Exception e){
             e.printStackTrace();
        try{
        Validator.main(null);
        }catch(Exception e){
             System.out.println("Validator exception");
             e.printStackTrace();
     public static Element createElement(Document doc, String tag,String prefix, String nsURI) {
          String qName = prefix == null ? tag : prefix + ":" + tag;
         return doc.createElementNS(nsURI, qName);
}Validator class:
import javax.xml.crypto.*;
import javax.xml.crypto.dsig.*;
import javax.xml.crypto.dom.*;
import javax.xml.crypto.dsig.dom.DOMValidateContext;
import javax.xml.crypto.dsig.keyinfo.*;
import java.io.FileInputStream;
import java.security.*;
import java.util.Collections;
import java.util.Iterator;
import java.util.List;
import javax.xml.parsers.DocumentBuilderFactory;
import org.w3c.dom.Document;
import org.w3c.dom.NodeList;
* This is a simple example of validating an XML
* Signature using the JSR 105 API. It assumes the key needed to
* validate the signature is contained in a KeyValue KeyInfo.
public class Validator {
    // Synopsis: java Validate [document]
    //       where "document" is the name of a file containing the XML document
    //       to be validated.
    public static void main(String[] args) throws Exception {
     // Instantiate the document to be validated
     DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
     dbf.setNamespaceAware(true);
     Document doc =
            dbf.newDocumentBuilder().parse(new FileInputStream("signedPurchaseOrder.xml"));
     // Find Signature element
     NodeList nl =
         doc.getElementsByTagNameNS(XMLSignature.XMLNS, "Signature");
     if (nl.getLength() == 0) {
         throw new Exception("Cannot find Signature element");
     // Create a DOM XMLSignatureFactory that will be used to unmarshal the
     // document containing the XMLSignature
     XMLSignatureFactory fac = XMLSignatureFactory.getInstance("DOM");
     // Create a DOMValidateContext and specify a KeyValue KeySelector
        // and document context
     DOMValidateContext valContext = new DOMValidateContext
         (new KeyValueKeySelector(), nl.item(0));
     // unmarshal the XMLSignature
     XMLSignature signature = fac.unmarshalXMLSignature(valContext);
     // Validate the XMLSignature (generated above)
     boolean coreValidity = signature.validate(valContext);
     // Check core validation status
     if (coreValidity == false) {
             System.err.println("Signature failed core validation");
         boolean sv = signature.getSignatureValue().validate(valContext);
         System.out.println("signature validation status: " + sv);
         // check the validation status of each Reference
         Iterator i = signature.getSignedInfo().getReferences().iterator();
         for (int j=0; i.hasNext(); j++) {
          boolean refValid =
              ((Reference) i.next()).validate(valContext);
          System.out.println("ref["+j+"] validity status: " + refValid);
     } else {
             System.out.println("Signature passed core validation");
     * KeySelector which retrieves the public key out of the
     * KeyValue element and returns it.
     * NOTE: If the key algorithm doesn't match signature algorithm,
     * then the public key will be ignored.
    private static class KeyValueKeySelector extends KeySelector {
     public KeySelectorResult select(KeyInfo keyInfo,
                                        KeySelector.Purpose purpose,
                                        AlgorithmMethod method,
                                        XMLCryptoContext context)
            throws KeySelectorException {
            if (keyInfo == null) {
          throw new KeySelectorException("Null KeyInfo object!");
            SignatureMethod sm = (SignatureMethod) method;
            List list = keyInfo.getContent();
            for (int i = 0; i < list.size(); i++) {
          XMLStructure xmlStructure = (XMLStructure) list.get(i);
                 if (xmlStructure instanceof KeyValue) {
                    PublicKey pk = null;
                    try {
                        pk = ((KeyValue)xmlStructure).getPublicKey();
                    } catch (KeyException ke) {
                        throw new KeySelectorException(ke);
                    // make sure algorithm is compatible with method
                    if (algEquals(sm.getAlgorithm(), pk.getAlgorithm())) {
                        return new SimpleKeySelectorResult(pk);
            throw new KeySelectorException("No KeyValue element found!");
        //@@@FIXME: this should also work for key types other than DSA/RSA
     static boolean algEquals(String algURI, String algName) {
            if (algName.equalsIgnoreCase("DSA") &&
          algURI.equalsIgnoreCase(SignatureMethod.DSA_SHA1)) {
          return true;
            } else if (algName.equalsIgnoreCase("RSA") &&
                       algURI.equalsIgnoreCase(SignatureMethod.RSA_SHA1)) {
          return true;
            } else {
          return false;
    private static class SimpleKeySelectorResult implements KeySelectorResult {
     private PublicKey pk;
     SimpleKeySelectorResult(PublicKey pk) {
         this.pk = pk;
     public Key getKey() { return pk; }
}PurchaseOrder.xml
<?xml version="1.0" encoding="UTF-8"?>
<PurchaseOrder>
<Item number="130046593231">
<Description>Video Game</Description>
<Price>10.29</Price>
</Item>
<Buyer id="8492340">
<Name>My Name</Name>
<Address>
   <Street>One Network Drive</Street>
   <Town>Burlington</Town>
   <State>MA</State>
   <Country>United States</Country>
   <PostalCode>01803</PostalCode>
</Address>
</Buyer>
</PurchaseOrder>signedPurchaseOrder.xml with XAdES namespace:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><PurchaseOrder>
<Item number="130046593231">
<Description>Video Game</Description>
<Price>10.29</Price>
</Item>
<Buyer id="8492340">
<Name>My Name</Name>
<Address>
   <Street>One Network Drive</Street>
   <Town>Burlington</Town>
   <State>MA</State>
   <Country>United States</Country>
   <PostalCode>01803</PostalCode>
</Address>
</Buyer>
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="Sig1"><ds:SignedInfo><ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/><ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/><ds:Reference URI=""><ds:Transforms><ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/></ds:Transforms><ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ds:DigestValue>tVicGh6V+8cHbVYFIU91o5+L3OQ=</ds:DigestValue></ds:Reference><ds:Reference Type="http://uri.etsi.org/01903/v1.3.2#SignedProperties" URI="#SignP"><ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ds:DigestValue>MAQ/vctdkyVHVzoQWnOnQdeBw8g=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>lSgzfZCRIlgrgr6YpNOdB3XWdF9P9TEiXfkNoqUpAru/I7IiyiFWJg==</ds:SignatureValue><ds:KeyInfo><ds:KeyValue><ds:DSAKeyValue><ds:P>/KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9
xD7nN1kuFw==</ds:P><ds:Q>li7dzDacuo67Jg7mtqEm2TRuOMU=</ds:Q><ds:G>Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0Nogps
QW5QvnlMpA==</ds:G><ds:Y>p48gU203NGPcs9UxEQQQzQ19KBtDRGfEs3BDt0cbCRJHMh3EoySpeqOnuTeKLXuFr96nzAPq4BEU
dNAc7XpDvQ==</ds:Y></ds:DSAKeyValue></ds:KeyValue></ds:KeyInfo><ds:Object Id="QualifyingInfos"><QualifyingProperties Target="Sig1" xmlns="http://uri.etsi.org/01903/v1.3.2#"><SignedProperties Id="SignP"/><UnsignedProperties/></QualifyingProperties></ds:Object></ds:Signature></PurchaseOrder>

I believe the problem is that you are not explicitly adding the xades namespace
attribute to the SignedProperties element before generating the signature. Thus,
the namespace attribute is not visible when canonicalizing, but when you serialize the
DOM tree to an output stream, (for reasons I'm not entirely sure why), the namespace
attribute is visible and is added to the SignedProperties element, which breaks the
signature.
You must always explicitly add namespace attributes using the Element.setAttributeNS
method. Try changing the following code from:
Element SPElement = createElement(doc, "SignedProperties", null,xadesNS);
to:
Element SPElement = createElement(doc, "SignedProperties", null,xadesNS);
SPElement.setAttributeNS("http://www.w3.org/2000/xmlns/", "xmlns", xadesNS);

Digital signature will not work in Reader

I need help I have been working on a new form I want to have digatally signed. I add the digital signature box, in the test pdf it pulls in my digital certificates and works. Once I save the form and try opening it with adobe reader 9 nothing happens when I click the signature block. On the other hand when it is opened in adobe pro the signatures work. I am saving the file as static and tried several combinations of options and nothing seems to work. Can anybody give me some easy to follow instructions? I am using version 8. I appreciate any help.

I am having the same problem with signatures. I am including a form in a pdf portfolio to collect signatures from different users who have Reader. I make sure that features have been extended for reader. Most of the time they are okay. But every once in a while (at least one every two weeks) I get a user telling me they can't sign. No message or error of any kind, just a quick blink but no signature. As a work-around I've had to save a copy and re-extend features. This can be time consuming when there are a few documents I need to circulate. Please advise.

Digital Signature In PO (For release)

Dear All,
Please tell me something abt digital sign.
If I relaese PO through me29n then I will have to perform another activity (additional T code) for the digital signature.
Tell me related T-codes for the same.
Thanks in advance.
Regards
Gitesh

Hi AP,
Actually I am not aware of this digital signature scenario.
So Pls tell me in datail.
Regards
Gitesh

More then one digital signature on Form 16

Hi,
Our client want to use digital signature on the basis of Compnay code.
Presently one signature we uplaoded and the same is used fro all compnay codes.
We want to use signature on the basis of company code.
How to do the same, please help me.
We r on ECC 6.00 with SP level 42
Regards
Sanjay M.

Shyam,
I have a similar issues and looking for the <filename>.cer file to install the Trusted Anchor to validate digital signature in Adobe Interactive Forms.
Did you resolve this issue?
Can you please let me know where to get this file?
Thanks
Sundar

Digital signature on PDF file from C#

I want to add digital signature on PDF file from C# code. I understand from web that there are some third party license required, or I would need to use Adobe Acrobat to apply digital signature on PDF using acrobat APIs.
What is the licensing mechanisim for acrobat is APIs? What is the cost effective way for applying digital signature on PDF files.

Hi, Use C# to create signature on PDF. You can refer to my link http://www.e-iceblue.com/Knowledgebase/Spire.PDF/Program-Guide/How-to-Create-PDF-Digital-S ignature.html

SSF Digital Signature

Dear Experts,
Am trying to invoke digital signature process using SSF with SAP username/password. When i give by SAP password and do a signing i get the following error message:
Ssf_GetOwnCertificate: SsfOpenProfile failed with rc=23
I also have a external security product. but initially i would like to test this feature with SAP username/password and then move on to the external security product for this process.
Can someone help me out on this.
Regards,
Karthik

Hi,
I checked with SSF01 and found that am able to apply the digital signature in this for testing. Also using a third party product without verification is also working fine.The problem i face is with SAP username/password and also with Third party product with verification.
Can you think of something that might have gone wrong.
Regards,
Karthik

Digital Signature Check Printing issue

Hi ,
I have one issue in check printing for Tcode : F110 .
When i take printout signature comes below the line   , i want to move digital signature above the line .
in Script Code is like this
T3
T3
/:           HEX TYPE PCL LEFT '5.00' CM
/=           1B2831511B2873317033362E307630733062305453
/:           ENDHEX
Now Can you tell me how to move signature from below the line to Above the line .
Regards,
Sandeep Jadhav

Hi,
When you say adjustment how did you pass the adjustment ? what transaction code was used? normally to post a payment without printing check you can use F-53 and that should not print any checks.
Thanks and Regards
K.Raghavendran

Digital Signatures/Javascript After Signing?

Hello everyone,
I'm currently developing forms for my company, post processed through Adobe Acrobat 9 Standard, that require digital signatures. Working in the food industry requires compliance to specific FDA guidelines, specifically CFR 21 part 11. In order to meet the requirements I must develop an SOP (Standard Operating Procedure) that proves signatures are accurate and secure.
The process is tedious, and I have called a few meetings thus far to discuss some of the unforseen circumstances. During the discussion a question was brought up stating; What protects forms stored in the archives (3 years for compliance) from being corrupted by a disgruntled employee? Specifically, what stops an employee from clearing a digital signature? I realize we can set up file access rights to the forms to prevent such happenings, but majority of the forms are setup to hold 6 months to a year of info, thus wouldn't be archived until filled completely.
My question: Does anyone out there know of a javascript or trick to disable the "Clear Signature" function after signed? I've been searching and have turned up empty handed. Also, does anyone have any other javascripts that are used after digital signature occurs?
Thanks in advance for any help you can give me,

George,
Thanks for your response.
The issue is not if the file is deleted, the issue is if the files becomes "manipulated". I think "corrupted" was the wrong choice of words.
To explain: Any form that is completed has several digital signatures within the contents, depending on which QA Technicians complete the task (e.g. Calibrations, Metal Detector Settings, etc...). Forms are setup by days, weeks, or in some cases years, and have designated signature areas for the time period the test was conducted. So, after "John Smith" completes his portion of the form he is required to digital sign the document, after signing is complete all information is set to read only and cannot be altered unless the signature is deleted.
Digital signatures can be deleted in two ways:
1. The user who signed the document, based on active directory, has the ability to "clear signature". As and FYI: no other user is capable of deleting a signature signed by another employee. (does not apply to the form author)
2. The file creator can add a "Reset button" control, thus being able to delete any data specified.
So as I said I'm looking for a way to lock all signature functions, after sign is completed, even for the original signer. So if form "Calibration01" is currently being filled out and has signatures x,y,and z on it; I want to make sure if "x" is disgruntled they do not maliciously go and clear their signature. Also, I would like all fields associated with the signature to be locked without any way for the user to manipulate or revise data.
If anyone has any javascripts that run once signer digitally signs, it would be a great help,
Thanks,

Do AVI Compression Filters require a Microsoft Digital Signature in LV

Hello all,
        My company has written a custom video codec. I installed the custom codec onto my machine. When I did I was warned that this codec did not have "Microsoft Digital Signature". I said "ok" and installed it anyway. The codec appeared in my Hardware codec properties tab. I figured all was good. I was wrong.
         When I run the VI "IMAQ AVI get filter names" it does not appear in the returned list. I assumed the reason for this to be because the VI only returns Microsoft approved codecs. Am I right? I also tried using the codec by using a string constant and placing its name exactly how it appears in the HArdware properties tab into the "IMAQ AVI create" VI. This did not work either.
         Am I right by assuming that I cannot run non-microsoft approved codecs in IMAQ LV? Is there a way around this? Any feedback???
Foiled by MS,
Glen D.

Hey Glen D.,
The Get Filter Names VI returns only the filters that are able to work the NI's AVI functions. What the VI does is it gets the list of filters from DirectShow and then it tests each one with a sample frame to see if it can compress the image or not. Then the function returns a list of the codecs that work. This does not necessarily mean that the function works only with Microsoft approved codecs. So if your custom codec can somehow align with the DirectShow architecture, then your codec should be detected by the IMAQ AVI functions.
I hope this answers your question. Please let me know if you have any further questions or concerns. Thanks, and have a great day.
Regards,
DJ L.

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code

I get this message when I check the Device manager for my Ipod
Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)
How do I resolve this I have reinstalled iTunes but it still doesn't recognise my ipod

I reinstalled Itunes a couple of times. I unistalled all programs that I never use, I updated all of my drivers, Windows swept my computer and found no problems. I have a yellow causion lite when I look at the USB-port with the phone connected. All other devices work without a problem.

Digital Signatures for mutliple company code

Hi,
Our client have multiple company codes & they want to use digital signature for all the company code and there be individual authorised digital signatory for each comp code.
Now the question is , whether we have procure different digital signature for individual company codes & if so how system will identifies which authorised ditigatl signature should be assigned to respective company code...?
=> We are not able to download Adobe Form local & aslo is it mandatory to have digital signature to download Form 16 on a local system.
System details : ECC 6
SP Level : 38
Thanks & Regrads,

Digital Signature is person specific
You have to take the Digital signature ( A number assigned for each signatory with the tool),from an authorized services provided by NSDL
In a single company code if you have 2/3 signatories , first you need to make groups based on the signing authorities, in combination of PA/PSA/EG/ESG/BA etc
The form 16 is to be generated on the above criteria applicable.
3 file of form16 will be generated and send accross to 3 signing authorities
The signing authority can open the form using the tool ,digitial signatory software install and can authenticate the form16.
As per NSDL form16 is now not an statuory doucment. Its just an Tax Information of an Employee.
which is not required to be attached with your ITR's also
So why do you require the Digital signature to be printed on the form16 . Pls check this up with your finance team
Thansk & Regards
Hemant V. Mahale

Digital Signature filteration (eg: cn=TEST) Javascript code

Similar Messages

Maybe you are looking for