Skip to main content

Merging password protected PDF files in ColdFusion

In ColdFusion, CFPDF tag can be used to perform several PDF related operations such as adding a watermark, generating thumbnails, deleting pages, merging documents and securing a PDF with password. Today I wanted to merge all my bank statements into a single PDF document, such that only the first page from each document containing the summary of the statement is present in the merged document.

To merge these documents, one can use CFPDF tag with the action attribute set to 'merge'. However, the PDF files that I was trying to merge were password protected. To merge password protected files one can use the CFPDFPARAM tag within a CFPDF tag and provide password there:
 <cfpdf action="merge"  
     destination="merged.pdf"  
     overwrite="yes">  
      <cfpdfparam source="pdf1.pdf"  
            password="#password#"  
            pages="1">  
      <cfpdfparam source="pdf2.pdf"  
            password="#password#"  
            pages="1">  
      .
      .
      .
      .
 </cfpdf>

As mentioned earlier, the merged document should have only the first page from each document. The CFPDFPARAM tag with the pages attribute set to '1' would consider only the first page while merging. One can also specify a range of pages with "1-5" or a list of pages separated with a comma "1,5,7".

The resultant merged document was not password protected. To secure a PDF file with a password, one can use the CFPDF tag with the action attribute set to 'protect':
 <cfpdf action="protect"  
     source="merged.pdf"  
     newuserpassword="test">

Labels:

Comments

  1. JosephDecember 7, 2011 at 11:07 AM

    This comment has been removed by the author.

    ReplyDelete
  2. JosephDecember 7, 2011 at 2:44 PM

    I don't know how that works and I'm glad you shared this information with us. Now I know how to merge them in ColdFusion.

    long island document scanning

    ReplyDelete

Post a Comment

Popular posts from this blog

How to use the APP_INITIALIZER token to hook into the Angular bootstrap process

I've been building applications using Angular as a framework of choice for more than a year and this post is not about another React vs Angular or the quirks of each framework. Honestly, I like Angular and every day I discover something new which makes development easier and makes me look like a guy who built something very complex in a matter of hours which would've taken a long time to put the correct architecture in place if I had chosen a different framework. The first thing that I learned in Angular is the use of the APP_INITIALIZER token.
Post a Comment
Read more

On GraphQL and building an application using React Apollo

When I visualize building an application, I would think of using React and Redux on the front-end which talks to a set of RESTful services built with Node and Hapi (or Express). However, over a period of time, I've realized that this approach does not scale well when you add new features to the front-end. For example, consider a page that displays user information along with courses that a user has enrolled in. At a later point, you decide to add a section that displays popular book titles that one can view and purchase. If every entity is considered as a microservice then to get data from three different microservices would require three http  requests to be sent by the front-end app. The performance of the app would degrade with the increase in the number of http requests. I read about GraphQL and knew that it is an ideal way of building an app and I need not look forward to anything else. The GraphQL layer can be viewed as a facade which sits on top of your RESTful services o...
Post a Comment
Read more

Using MobX to manage application state in a React application

I have been writing applications using React and Redux for quite some time now and thought of trying other state management solutions out there. It's not that I have faced any issues with Redux; however, I wanted to explore other approaches to state management. I recently came across MobX  and thought of giving it a try. The library uses the premise of  `Observables` to tie the application state with the view layer (React). It's also an implementation of the Flux pattern wherein it uses multiple stores to save the application state; each store referring to a particular entity. Redux, on the other hand, uses a single store with top-level state variables referring to various entities.
Post a Comment
Read more