Paying back to internet

Silent pdf printing without applet

2009-11-10T06:35:00.000-08:00

I my current project I have to print a pdf without using an applet (all because the spanish electronic identity card ask for its password any time it open a connection). We have to do it silently, or a least with the less posible user intervention.

The idea is to insert an iframe which calls for the pdf, inside it we set javascript into the pdf for printing. I didn’t know that I could insert js into a pdf, but it is possible and easy with itext/itextsharp library.

Here is the page_load event in the page that returns the pdf. This is where all the magic is done:

   1: protected void Page_Load(object sender, EventArgs e)

   2:  {

   3:      MemoryStream ms = new MemoryStream();

4:

   5:      var urlPdf = new Uri(getBaseUrl() + "prueba.pdf");

6:

   7:      PdfReader ps = new PdfReader(urlPdf);

8:

   9:      /*inserts js into pdf*/

  10:      PdfStamper pdf = new PdfStamper(ps, ms);

  11:      pdf.JavaScript="this.print(false);";

  12:      pdf.Close();

13:

  14:      HttpContext.Current.Response.ClearContent();

  15:      HttpContext.Current.Response.ClearHeaders();

  16:      HttpContext.Current.Response.ContentType = "application/pdf";

  17:      HttpContext.Current.Response.AddHeader("Content-Disposition", "inline;filename=recibo.pdf");

  18:      HttpContext.Current.Response.BinaryWrite(ms.ToArray());

  19:      HttpContext.Current.Response.End();

  20:  }

And later we have just a page in which the iframe is inserted using jQuery:

   1: <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="SilentPDFPrinting._Default" %>

2:

   3: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

4:

   5: <html xmlns="http://www.w3.org/1999/xhtml" >

   6: <head runat="server">

   7:     <title></title>

   8:     <script src="js/jquery-1.3.2.min.js" type="text/javascript"></script>   1:  
   2:     <script src="js/default.js" type="text/javascript">
</script>

   9: </head>

  10: <body>

  11:     <form id="form1" runat="server">

  12:     <div>

  13:         <input id="Button1" type="button" value="button" onclick="printPDFSilently();" /></div>

  14:         <div id="diviframe"></div>

  15:     </form>

  16: </body>

  17: </html>

Here the jQuery:

   1: function printPDFSilently() {

   2: /*inserts an iframe which downloads the pdf*/

   3:     var jIframe = jQuery("<iframe id='iframehidden' src='/PdfPrinter.aspx' width='0' height='0' ></iframe>");

   4:     jIframe.insertAfter("#diviframe");

   5: }

As you can see it is very easy. Here you have the code

Hope this helps to anyone.

WSSecurity with jax-ws and WSS4J

2009-05-17T15:35:00.000-07:00

Hello everyone,

In my current project I have one non functional requisite quite challenging (at least for me, a dotnetboy playing around in the java world). As usual it came when the project was half made. It said… soap messages will be encrypted, ssl is not possible.

Well, so we have a few jax-ws services done, and ¡ups! jax-ws is incomplete (one friend told me it was like wcf, nothing further away from the truth, it leaks lots of ws-* features). The thing got harder because we have lots of differents app servers (tomcat, weblogic and jboss). I would be happy having the possibility of using Metro, but I need something independent.

So googling I found the first important thing: the jax-ws handlers. Basically it is a pre and post process of a message. We can modify the message just before is sent through the wire and before it get parsed by the service. How can we modify the service with a handler?

        2: @SOAPBinding

       3: @Stateless

       4: @HandlerChain(file = "../../../../../../handlers.xml")

       5: public class Service implements IService {

@HandlerChain points to the file which defines the classes which will be used as a handler.

       1: <?xml version="1.0" encoding="UTF-8"?>

       2: <jws:handler-chains xmlns:jws="http://java.sun.com/xml/ns/javaee">

       3:    <jws:handler-chain>

       4:       <jws:handler>

       5:       <jws:handler-class>

       6:             es.pablocastilla.WSSecurityHandler

       7:          </jws:handler-class>

       8:       </jws:handler>

       9:    </jws:handler-chain>

      10: </jws:handler-chains>

This classes should implement one special interface (as usual in this kind of things)

       1: public class WSSecurityHandler implements

       2:         SOAPHandler<SOAPMessageContext>

So know we have something in the service that will transform an encrypted message to a normal one.

And now, how do I code and decode the messages, well, all can be done with a few single classes:

       1: public class WSSecurityHandler implements

       2:         SOAPHandler<SOAPMessageContext>, CallbackHandler {

       3:  

       4:     Properties prop;

       5:  

       6:     /**

       7:      * Constructor initializes properties

       8:      * */

       9:     public WSSecurityHandler () throws Exception {

        prop = PropSingleton.getSingleton().GetProp();

    }

  

  

    /**

     * Returns special headers.

     */

    public Set<QName> getHeaders() {

        Set<QName> HEADERS = new HashSet<QName>();

  

        HEADERS.add(new QName(WSConstants.WSSE_NS, "Security"));

        HEADERS.add(new QName(WSConstants.WSSE11_NS, "Security"));

        HEADERS.add(new QName(WSConstants.ENC_NS, "EncryptedData"));

  

        return HEADERS;

    }

  

    /**

     * Handles the message, code and decode it depending if it is an outgoing or incoming one.

     */

    public boolean handleMessage(SOAPMessageContext messageContext) {

        try {

            // got the message from the context

            SOAPMessage msg = messageContext.getMessage();

  

            

            // is outgoing?

            Boolean isOutGoing = (Boolean) messageContext

                    .get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);

  

           

            if (isOutGoing) {

                // if it is outgoing code and sign

                EncryptUtil.EncryptSOAPEnvelope(msg, prop);

                EncryptUtil.SignSOAPEnvelope(msg, prop);

            } else {

                // if it is incooming decode and check signature.

                EncryptUtil.CheckSignAndDecode(

                        msg, this, prop);

            }

  

        } catch (Exception ex) {

            ex.printStackTrace();

            throw new RuntimeException(ex.getMessage());

        }

  

        return true;

    }

  

    public boolean handleFault(SOAPMessageContext messageContext) {

        return true;

    }

  

    /**

     * Return the jks key, not necesary

     */

    @SuppressWarnings("deprecation")

    public void handle(Callback[] callbacks) throws IOException,

            UnsupportedCallbackException {

  

        String password;

  

        for (Callback cb : callbacks) {

            if (cb instanceof WSPasswordCallback) {

                WSPasswordCallback pc = (WSPasswordCallback) cb;

  

                try {

                    password = prop.getProperty("password");

                } catch (Exception e) {

                    throw new UnsupportedCallbackException(pc,

                            "fallo al recuperar la clave en el properties");

                }

  

                if (pc.getIdentifer() != null) {

                    pc.setPassword(password);

                }

            }

        }

    }

  

    public void close(MessageContext messageContext) {

    }

  

  

}

The class which uses Apache´s WSS4J for encrypting the messages:

       1: public class EncryptUtil{

       2:  

       3:     @SuppressWarnings( { "unchecked", "deprecation" })

       4:     static void CheckSignatureAndDecode(SOAPMessage msg,

       5:             CallbackHandler cb,Properties prop) throws WSSecurityException,

       6:             TransformerConfigurationException, TransformerException,

       7:             SOAPException, IOException, Exception {

       8:  

       9:         WSSecurityEngine secEngine = new WSSecurityEngine();

        WSSignEnvelope signer = new WSSignEnvelope();

  

        String alias = prop.getProperty("alias");// login of jks file

        String password = prop.getProperty("password");// password of jks file

  

        signer.setUserInfo(alias, password);

  

        Crypto crypto = CryptoFactory.getInstance(prop);

        org.w3c.dom.Document doc = toDocument(mensaje);

  

//after we set the encrypt stuff the processsecurity does all the work

        Vector v = secEngine.processSecurityHeader(doc, null, cb, crypto);

  

        if (v == null) {

  

            throw new Exception("Access not granted.");

  

        }

  

        //put the decoded message into the object

        updateSOAPMessage(doc, msg);

    }

  

    /**

     * Updates the message with the unencrypt form

     */

    private static SOAPMessage updateSOAPMessage(Document doc,

            SOAPMessage message) throws SOAPException {

        DOMSource domSource = new DOMSource(doc);

        message.getSOAPPart().setContent(domSource);

        return message;

    }

  

    /**

     * Changes the SOAPMessage to a dom.Document.

     */

    public static org.w3c.dom.Document toDocument(SOAPMessage soapMsg)

            throws SOAPException, TransformerException {

        Source src = soapMsg.getSOAPPart().getContent();

        TransformerFactory tf = TransformerFactory.newInstance();

        Transformer transformer = tf.newTransformer();

        DOMResult result = new DOMResult();

        transformer.transform(src, result);

  

        return (Document) result.getNode();

    }

  

    /**

     * Signs  a SOAPMessage

     * 

     * @param mensaje

     * @throws Exception

     */

    @SuppressWarnings("deprecation")

    static void SignSOAPEnvelope(SOAPMessage mensaje, Properties prop) throws Exception {

        // WSSignEnvelope signs a SOAP envelope according to the

        // WS Specification (X509 profile) and adds the signature data

        // to the envelope.

        WSSignEnvelope signer = new WSSignEnvelope();

  

        

  

        String alias = prop.getProperty("alias");// "autentiaserver";

        String password = prop.getProperty("password");// "changeit";

  

        signer.setUserInfo(alias, password);

  

        Crypto crypto = CryptoFactory.getInstance(prop);

  

        Document doc = toDocument(mensaje);

        signer.setMustUnderstand(false);

        Document signedDoc = signer.build(doc, crypto);

  

        DOMSource domSource = new DOMSource(signedDoc);

        mensaje.getSOAPPart().setContent(domSource);

  

    }

  

    /**

     * Codes a SOAPMessage.

     */

    @SuppressWarnings("deprecation")

    static void EncryptSOAPEnvelope(SOAPMessage mensaje,Properties prop) throws Exception {

        // WSSignEnvelope signs a SOAP envelope according to the

        // WS Specification (X509 profile) and adds the signature data

        // to the envelope.

        WSEncryptBody encriptador = new WSEncryptBody();

  

        String alias = prop.getProperty("alias");

        String password = prop.getProperty("password");

        encriptador.setUserInfo(alias, password);

  

        Crypto crypto = CryptoFactory.getInstance(prop);

  

        Document doc = toDocument(mensaje);

        encriptador.setMustUnderstand(false);

        Document signedDoc = encriptador.build(doc, crypto);

  

        DOMSource domSource = new DOMSource(signedDoc);

        mensaje.getSOAPPart().setContent(domSource);

  

    }

  

    

}

All this stuff needs a jdk and some configuration. It is the one which should be place with the properties object which is seen in the classes. Some are repeated, you can improve that code :P

       1: org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin

       2: org.apache.ws.security.crypto.merlin.keystore.type=jks

       3: org.apache.ws.security.crypto.merlin.keystore.password=password

       4: org.apache.ws.security.crypto.merlin.keystore.alias=login

       5: org.apache.ws.security.crypto.merlin.file=/home/webuser/certs/beaclient/keystore.jks

       6: alias=login

       7: password=password

So we have a jax-ws service using WSSecurity :).

libs needed can be found here:

http://ws.apache.org/wss4j/

Hope it can help you, any comment will be appreciated. I am sorry, but I have no time for developing a working example.

Regards.

Why do I write this blog?

2009-05-17T15:30:00.001-07:00

Well, I have been working in IT for 5 years. In all this years I have just received help from google, books in amazon and good mates. So I want to help other people publishing my solutions.