XML Signature with Barcoded Form

I have a form that has a number of fields that need to be filled out. When this is complete, the user should digitally sign (with a certificate) the form. However, due to legal requirements, the form must then be printed and mailed back to the organization. Is it possible to encode the signature data within the barcode (PDF417) so it can be validated?

After finding the sign function and playing around with the resulting XML Signature, I've found it's just too much data to put in a barcode, even a 2D one.

Similar Messages

Is it possible to CREATE an XML data with Smart Forms??

Hello at all,
i have an Smart Form Formular, which contains all information about a customer.
My question is, if i want to send this Formular to another System, can I send this as a XML File or something else???
I have no idea, how i can send my smart forms formular to another System.
With kind regards.
ETN

I guess you want to send "spools" in XML format, not the definition of smart forms. So, the XML for Smart Forms is called XSF: read [SDN article - SAP SMART FORMS XSF - XML OUTPUT FOR SMART FORMS|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0b6bc290-0201-0010-5b87-a0e7c7eb55d0] and [sap library - smart forms - output in XSF format|http://help.sap.com/saphelp_nw70/helpdata/EN/a5/28d3b6d26211d4b646006094192fe3/frameset.htm]

Generating XML signature with prefix dsig ?

Hi everyone,
I'm facing a problem generating a signature of XML document. I'm using Jwsdp and the apache toolkit. So far, I can generate the signature of this form :
<Signature>
<SignedInfo> .....
I would like to generate the signature like this :
<dsig:Signature>
<dsig:SignedInfo> ....
The API doesn't specify how to add the prefix dsig befor tags element ...
It's very important for me to solve the problem, so any help would be really really appreciated :-)
Thanks a lot.

There is a method in DOMSignContext to do that:
// org.w3c.dom.Document doc;
DOMSignContext dsc = new DOMSignContext(privateKey, doc.getDocumentElement());
dsc.putNamespacePrefix(XMLSignature.XMLNS, "dsig"); // or "ds" which is my case

XML Signature with WSDL

Hello!!!
I created this topic also at Security forum, but i think that was a wrong choice
I need to consume Web Service (WSDL). It's working without any problem. But there is also one operation where I need to add Digitial Signature to it.
It is very hard to find any documentation how to configure signing XML messages in SAP. I was looking for SSF which should fit to my requriements. Then I found something like WS Security in LPCONFIG - but i don't know how to use it. I put there Profile OUT, but nothing happen. Could you give me some directions where to look for this?
To generate proxy i used SE80. I have only ABAP instance (but if there won't be any other choice i can install AS JAVA as well). No PI system in landscape.
Best regards
Rob

Are you doing digital signing transport level or message level?
Transport level:
if you do transport level then share the end system certificate in PI keystore and use https communication. Use Soap receiver adapter.
Message level:
If you need to message level digital signature then you might want to explore WS adapter. THis adapter supports digital signing as well WS Reliable Messaging Protocol. You have to configure WS adapter as receiver for this. Refer SAP help document on WS adapter for this. If there is a limitation to use WS adapter on this area, then you might have to do java mapping using Apache Axis software for digital signing. This requires more java effort.

Update XML files with HTML forms...

Hi,
I would like to know if its possible to update or insert data
to XML files from a HTML form? And how can I do it?
Does dreamweaver have any extension that does this?

hi bregent!
im using php.
i have a xml flash slide show script, and i want to insert
this slide show on a site. No problem here, but i would like to
create a backoffice were i can update or insert the pictures of the
xml slide show.
can you help me on this?

Generete xml doc with dtd form

Hi,
I am trying to generate xml doc based on dtd kind format.
I use following code to get my xml doc is ok based on dtd like
-----------dtd file---------------
<!ELEMENT client_data (client_job*, person*)>
<!ELEMENT client_job (job_cd, job_title?, primary_responsibilities?, grade_cd?, br_job_cd, eeo_job_group_id, effective_date?, end_date?)>
<!ATTLIST client_job errMsg CDATA #IMPLIED>
<!ATTLIST client_job deleteFlag ( Y | N ) 'N'>
<!ELEMENT job_cd (#PCDATA)>
<!ELEMENT job_title (#PCDATA)>
<!ELEMENT primary_responsibilities (#PCDATA)>
<!ELEMENT br_job_cd (#PCDATA)>
<!ELEMENT eeo_job_group_id (#PCDATA)>
-----------------end dtd--------------
OracleXMLQuery qry = new OracleXMLQuery(conn, sql);
qry.setRowsetTag("client_data");
qry.setRowIdAttrName(null);
// qry.useNullAttributeIndicator(true);
qry.useLowerCaseTagNames();
qry.setRowTag("client_job");
xmlDocToReturn = qry.getXMLDOM();
But if my dtd like following, i.g. has tree level, and data from multiple tables, the above code doesn't work for thes case
--------------tree level dtd----------------
<!ELEMENT person (person_name)>
<!ATTLIST person person_id CDATA #REQUIRED>
<!ATTLIST person hire_date CDATA #IMPLIED>
<!ATTLIST person effective_date CDATA #IMPLIED>
<!ATTLIST person end_date CDATA #IMPLIED>
<!ELEMENT person_name (formatted_name*, given_name*, prefered_given_name?, middle_name?, family_name*, affix*)>
<!ELEMENT formatted_name EMPTY>
<!ATTLIST formatted_name type ( presentation | legal | sortOrder) 'presentation'>
<!ELEMENT given_name (#PCDATA)>
<!ELEMENT prefered_given_name (#PCDATA)>
<!ELEMENT middle_name (#PCDATA)>
<!ELEMENT family_name (#PCDATA)>
<!ATTLIST family_name primary ( true | false | undefined ) 'undefined'>
-----------------end dtd -------------------
I try to use XMLDocumentFragment to create xml doc and appendChild , but the xml doc is not the format of the dtd required. Can you give me a Java sample?
Thanks in advance.
Yan

Why don't you use XSLT?

Problem with XML signature

Can anybody tell me how to generate an xml signature
with the base 64 transform(Transform.BASE64)?
I just can't find any documentation on the web.
It would be great to provide a small code exemple.
Thanks
Antoine

Thanks for the reply.
I'm applying appropriate namespaces to the generated xml string. Could it be the probelem?
this is how the generated xml looks in final stage, I mean after I'm doing some rework on the generated xml.
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><Reference URI="#PAYMENTS"><Transforms><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue>IXgHx5ioixsJ13jyg767D8UCU9s=</DigestValue></Reference></SignedInfo><SignatureValue>DO+Fngf3h0Q5iDoMq2mZFL+bxL3vY1i1fyqzBbKRPhHlzqWrW2wP3SFHjVzPLXdj92W8hMx9I8Jq
QBV/D+pUKa32aZB7kPwOGZqR63X+d6Hca58jnTK7+zq8Fzi2DPlE+omQhgT3xeXp/lQpKI8vAgVT
eX+eylRYTAZDSfDw7qk=</SignatureValue><Object Id="PAYMENTS"><PAYMENTS xmlns=""><Payment><PaymentIdA></PaymentIdA><PaymentIdB>aa</PaymentIdB><SrcBank>bb</SrcBank><SrcAccount>cc</SrcAccount><PayerId>dd</PayerId><PayerName>Dato</PayerName><TaxPayerId>00022023</TaxPayerId><TaxPayerName></TaxPayerName><ReceiverName>mof</ReceiverName><AdditinalInfo>racxa</AdditinalInfo><Amount>521</Amount><TreasuryCode>hello</TreasuryCode><PaymentTime>hi</PaymentTime><PaymentChannel>ib</PaymentChannel></Payment></PAYMENTS></Object></Signature>

Need to Merge an Adobe XML file with a normal PDF

The problem...
I have created an order form in Adobe LiveCycle Designer (pre-ES). The customer's requirements force us to merge their purchase order (a flat standard PDF) with the order form I have created to get the complete PDF to bill with. Previously we were using a form created in another software and printing to PDF to merge the 2 PDF files. The thought process with creating a form in LiveCycle Designer was "Oh 2 PDF's we can just merge them" ... we were very WRONG. And please don't suggest "Packaging" the files... it won't work for our processing system... we've already tried .
What we know now (had we known it before we'd have never purchased the licensing for LiveCycle Designer to start with)...
You can NOT merge a PDF that has XML in it with Adobe Proffesional.
Temporary Solution...
We know we can print to PDF and then merge the files... this gets us the result we need, but it takes longer to print to PDF from these XML files than it did from the previous versions of the order forms in created in other software.
Is there another solution?
Plea for help! The users that are forced to do the process of printing to file and merging are ready to riot and/or go back to the "other" software.

Hello!
There are a couple terms you can google:
"PDF Concatenate Forms iText"
"Merge XML data with PDF Forms"
Concatenating PDFs means you join multiple forms together into one PDF.
Did you need to merge, or concatenate the forms?
Either way there are a couple of methods to do this programmably.
iTextSharp (.NET)
iText (Java)
FDFToolkit.net (.NET)
iText products are open source, and have a learning curve, and support is provided on a Open mailing list.
iText products are free ($) but can cost you time and money to research the methods.
Useful Links:
http://www.fdftoolkit.net/
Message was edited by: NKOWA

Barcoded form with XML-data

Hi all,
In our solution we have some barcodes on a form (7 barcodes on the one that I am using), they contain compressed XML data (I know that this uses much space in the barcode - anyway it should work regardless of this).
What the interesting thing is what is returned from the "decode-service" in WB.
When I run a scanned form through the process I have created I get "garbled" xml in my XML-doc that is returned from the decode-service.
If I use a handheld scanner (with a customly created program that handles the compression) I get the correct data from the barcode.
If I do not use compression in the barcode I get the correct XML data from the barcode (with the decode-service). This is weird to me... What is going on???
Some time ago I posted this issue (http://www.adobeforums.com/webx?128@@.3c058293) but never really caught up with a solution.
Can you help me with this?
Sincerely
Kim

Oops, something happended with the above post. I will try again... I have tried your suggestion but I still get the same garbled XML (with data repeated and some values "cut in half". Here is what I get after decode-service and extract-to-XML-service. This is just the first barcode, the others are similar, sorry for the poor formatting, but I get a CDATA tage infront of the "istensen" value. CDATA:istensen</fld_ForMellemEfterNavn ><fld_VejNRpostByEnLinie >Superroad 99, 1330 Supertown</fld_VejNRpostByEnLinie ><fld_PrivatTelefonnummer >20724283</fld_PrivatTelefonnummer ></sub_Person ></sub_PktA ><fld_BlanketNr >kb0371ff</fld_BlanketNr ><fld_BarcodeCount /></form1 >/sub_Adresse ><sub_Person ><fld_ForMellemEfterNavn>Kim Christensen</fld_ForMellemEfterNavn ><fld_VejNRpostByEnLinie > Superroad 99, 1330 Supertown </fld_VejNRpostByEnLinie ><fld_PrivatTelefonnummer >20724283</fld_PrivatTelefonnummer ></sub_Person ></sub_PktA ><fld_BlanketNr >kb0371ff</fld_BlanketNr ><fld_BarcodeCount /></form1 Obviously this is not a legal xml-string, so I can do nothing about it. I have tried using a custom .NET component (ClearImage) for reading the same form (with the barcode) I get the correct data out from the barcodes. So I guess something is wrong with the decode-service in Barcoded Forms ES when I use compressed XML. But I can conclude since the ClearImage component can read the barcodes that they are compressed correctly. Can you help me with getting further with this problem? Sincerely Kim

Web Service Security with SAML - Invalid XML signature

Hello together,
we want to build a scenario where we want to use Web Service Security with SAML.
The scenario will be
WS Client (Java Application) -> WS Adapter -> Integration Engine -> WS Adapter-> CRM (Web AS ABAP 7.01 SP 3)
SAP PI release is 7.11 (SP Level 4)
We want to use the SAML Authentification from WS Client to PI and from PI to Web AS ABAP.
The SAML authentifications between the WS Client and PI works when there is no SAML auth between PI and CRM.
But we get following error at calling the CRM system when we want to communicate with SAML:
<E_TEXT>CX_WS_SECURITY_FAULT:Invalid XML signature</E_TEXT>
Has somebody an idea of the possible reason for the error.
Thanks in advance
Stefan

Error Messages in the Trace/Log Viewer:
CX_WS_SECURITY_FAULT : Invalid XML signature | program: CL_ST_CRYPTO==================CP include: CL_ST_CRYPTO==================CM00G line: 48
A SOAP Runtime Core Exception occurred in method CL_ST_CRYPTO==================CM00G of class CL_ST_CRYPTO==================CP at position id 48 with internal error id 1001 and error text CX_WS_SECURITY_FAULT:Invalid XML signature (fault location is 1 ).
Invalid XML signature

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

How to delete hyperlink (Remove signature) in a form created with InfoPath

Hello.
We have Sharepoint 2013 Foundation in production. It work with forms created with InfoPath. In these forms, digital signatures are used to approve. The problem is that once you have signed the forms, the user can remove the signature. That's what we want to
avoid.
Which file should I edit to remove the hyperlink? I can not find how to do it. Do you know a better option?
Greetings.
MCSA: Windows Server 2008

Hi,
According to your post, my understanding is that you want to delete hyperlink (Remove signature) in a form created with InfoPath.
As far as I know, there is no OOTB way to achieve this. You need to use custom code to prevent removal of digital signatures.
Please add the OnBeforeChange handler code to the "signatureN" group where the signature is stored, not to the section you are signing.
In other words (my excample) browse to :
Tools - Form Options - Digital Signatures - "Enable digital signature for specific data" - Modify/Add
Note the "Store signatures in the following group" value. It will be a read only value, eg /my:myFields/my:signature3/my:signature4
Here is a similar thread for your reference:
http://www.infopathdev.com/forums/p/3661/12829.aspx#12829
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Transforming signed XML document with namespace invalidates signature

I am running into a problem signing an XML document. Well, signing the document isn't the problem, as I can sign it and then verify the signature with the public key successfully. The problem comes when I transform the document to a string. It all appears to be OK, but when I transform it back, the hash no longer verifies. After more testing, it appears that the issue is related to namespaces. When I remove namespaces from the document, the signing and transformations work just fine. Does anyone have any insight on this?
Here is how I am transforming the document to an XML string that I and back.
    try
      signSAML( doc, assertionElement );
      xmlSource = new DOMSource( doc );
      baos = new ByteArrayOutputStream();
      outputTarget = new StreamResult( baos );
      xmlString = new String( new ByteArrayInputStream( baos.toByteArray() ) );
      transformerFactory = TransformerFactory.newInstance();
      transformer = transformerFactory.newTransformer();
      transformer.transform( xmlSource, outputTarget );
      boolean verified = verify( doc );
      if ( verified )
        System.out.println( "Verified" );
      else
        System.out.println( "UNVerified" );
    catch ( Exception e )
      // TODO Auto-generated catch block
      e.printStackTrace();
    }

jtahlborn wrote:
i'm not talking about the transform, i'm talking about this line:
xmlString = new String( new ByteArrayInputStream( baos.toByteArray() ) );which is a great way to break xml data.Yes. That's not the only kind of data it's good at breaking, either.
To the OP: just have your transform output to a StringWriter in the first place. Don't muck about converting between chars and bytes unless you know the correct encoding and use it. Which you don't know it and you didn't use it.

Form with barcodes

I want to use a form with barcodes created from another text field.
The forms are created with acrobat professional and work fine with acrobat pro.
WIth acrobat reader on pc, de barcode turns grey.
On my iPad the barcodes won't even change at all.
Is there a way to update the barcode using Adobe reader iOS?
javascript ?
Thx.

Currently, Adobe Reader for iOS does not support barcodes. Sorry for the inconvenience.
For general Forms questions regarding Acrobat Pro and Adobe Reader (desktop applications), I'd recommend posting questions to the PDF Forms forum for further assistance. Thank you.

MTOM combined with WS-Security (XML signature)

I'm testing the support of MTOM together with WS-Security (XML-DSIG) on OEG. When verifying the XML signature I noticed I had to add the "Insert MTOM attachments"-filter first. Is this the right way? Shouldn't the signature verification do this transparently?
My other question is how OEG handles the attachments? Does it page them to disk? What happens if my attachments are very large? With the default setup of OEG I encountered out-of-memory issues with attachments above 200MB
Edited by: wsalembi on Sep 22, 2011 12:45 AM

If you just sign the <xop:Include> element, you are effectively only signing the reference to the attachment, i.e. the value of the href attribute. This will only prevent someone changing the href to point to a different attachment.
If you in-line the base64 encoded contents of the attachment into the XML message and only sign the base64 encoded string, you are only preventing anyone from changing the contents of the attachment.
You are not stopping somebody from changing what the <xop:Include> href attribute points to.
So I think there is value in signing BOTH the contents AND the <xop:Include> element so that:
- The integrity of the contents of the attachment is ensured, and
- The integrity of the reference to the attachment in the <xop:Include> element is ensured.
Interestingly, the XOP spec acknowledges this issue in Section 6.1:
http://www.w3.org/TR/xop10/#package_integrity
6.1 XOP Package Integrity
The integrity of Infosets optimized using XOP may need to be ensured. As XOP packages can be transformed to recover such Infosets (see 3.2 Interpreting XOP Packages), existing XML Digital Signature techniques can be used to protect them. Note, however, that a signature over the Infoset does not necessarily protect against modifications of other aspects of the XOP packaging; for example, an Infoset signature check might not protect against re-ordering of non-root parts.
In the future a transform algorithm for use with XML Signature could provide a more efficient processing model where the raw octets are digested directly.
In OEG, it would be possible to use 2 XML Signature Validation filters with an Insert MTOM Attachment filter to validate both signatures.
The flow in the policy would be as follows:
1. 1st XML Signature Filter :- Validate the Signature over the <xop:Include> element
2. Insert MTOM Attachment Filter :- Inline the base64 encoded contents of the attachment
3. 2nd XML Signature Filter :- Validate the Signature over the element now containing the in-lined base64 encoded data.
This policy would ensure the integrity of the attachment contents AND the reference to this attachment in the <xop:Include> element.

XML Signature with Barcoded Form

Similar Messages

Maybe you are looking for