We're building an Adobe PDF form that will be downloaded from our website, filled out by clients, and then emailed back to us. We need each PDF sent back to us from email to be encrypted. And when we receive it on our end we need to use C# to read the decrypted PDF. I know there's a way for the user to add a password within the UI of Adobe PDF. Is there a way to add the password within the Adobe PDF code?
On the Adobe website the only options I can find are to use external tools or Adobe's cloud platform.
Related
A client has asked that I include a "View in browser" link to a pdf attached to an email. This should open the same PDF in the user's default web browser. I have a PDF editor (PDFescape Desktop) that I can successfully use to add links to webpages, and it seems capable of opening files, and even executing javascript, though I've never tried it (I am proficient in JS though so that's an option if anyone has any ideas).
The only thing I can think of is to host the PDF somewhere and then link to it's location, but I'd rather not use a third party server if I can help it.
Is there any way to reference a link in a PDF to the same PDF the link exists in?
How to encrypt pdf files and display them in web in a way that the data is encrypted in the inspect element and no one can see the direct link so that cannot be downloaded.
Is there any web service or software to do this?
Do you mean you want prevent them from save?
We are trying to sign a Tiff file using CoSign but it is showing error: "File is not supported".
Is it possible to Sign a Tiff using CoSign via web-agent API or via back-end.
Or please suggest if any alternate is there.
The CoSign Web Agent doesn't sign tiff files. It can be used to sign PDF, Word, and Excel files in their native formats. It can also automatically convert Word and Excel files to pdf format.
Tiff files can be signed via CoSign in any of three ways:
CoSign Signature API
Docs. This is a new API and there are some issues with the documentation. Please see other questions about this API and ask additional questions if you have a problem.
CoSign Signature SOAP API
Docs This API's Sign method can sign tiff files.
CoSign Signature Local API
Docs This is a Windows local API. It can also be used to sign tiff files.
I am exporting crytsal report to pdf format and saving the pdf on azure cloud. This code is written in web api. I am also able to download the pdf on client. Is there any way with which I can open this saved pdf file on client side by either using server side code or using jQuery. I just want to keep the file open for the user to view.
Maybe you can have a link point to the PDF file address with response header "response-content-disposition": "inline; filename=this.pdf", "response-content-type": "application/pdf". Then I think the browser will launch proper PDF plugin to show it.
We are building a web application(Java). Could anybody help brief me what we need to realize the following business scenario ?
An user access our web site
He inputs some data
He generate a PDF file from the data he input and export it
He digitally sign this PDF file
He then upload this PDF file to our web site
The system can parse the PDF file to know who signed this file and be sure it is of integrity and Non-repudiation and to some post-processes.
My questions are:
What products/libraries(commercial or free opensource) should I need to implement the above ?
Do those products provide API for developers to programmatically operate the signing process and retrieve information from a signed documents ?
Is it a reasonable or proper way to do the digital signature in the above 3~5 steps ? could the user sign the data online in one step(e.g., without export a PDF file) ?
iText is a java library which, amongst other things, enables you to sign and verify signatures on pdf documents. This would enable your users to sign a pdf online. A good example of using iText for signing and verifying signatures in pdf documents can be found here
The library's licence is AGPL i.e. you need to release your software under AGPL or buy a commercial licence.
It used to be under the LGPL so you can work with iText 2.1.7 under the terms of LGPL and not need to buy a commercial licence.
If the data is located on the client, then your easiest option is to create a Java applet which will be executed in browser, and which will sign the data. Any data can be signed, and you don't need PDF just for signing. Generic binary data can be signed using PKCS#7/CMS format or using XMLDSig (less widespread option).
For signing data in Java applet you can use BouncyCastle or our SecureBlackbox (Java edition). BouncyCastle is open-source and SecureBlackbox comes with support, documentation and samples.