Opening Encrypted/Certificate Secured PDF.

Hello,
I have a pdf encrypted using certificate. I want to open this pdf using Acrobat sdk APIs. I have read the documentation of "Opening secured Pdf". I learnt that AVDocOpen() function calls Acrobat built in authorization procedure and using PD layer to open a encrypted pdf we need to write our own authorozation procedure. I want some example which demostrates how encrypted pdf are opened. Also, when opening certificate secured pdf, where does Acrobat installs the certificate?
Please can someone guide me!!
Thanks in advance.

Yes, you can read XMP w/o opening the PDF – of course, that assumes that the XMP is not encrypted (it's a choice of the PDF authoring/encrypting tool).
From: Adobe Forums <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Date: Mon, 16 Jan 2012 21:10:56 -0800
To: Leonard Rosenthol <[email protected]<mailto:[email protected]>>
Subject: Opening Encrypted/Certificate Secured PDF.
Re: Opening Encrypted/Certificate Secured PDF.
created by poortip87<http://forums.adobe.com/people/poortip87> in Acrobat SDK - View the full discussion<http://forums.adobe.com/message/4145422#4145422

Similar Messages

  • PDF with a certificate security.

    I am trying to secure mutiple PDF documents with a certiciate security. If I am understanding the certificate security feature correctly, I'd like to add multiple emails to these documents so that only the recipients listed in the email certificate security can open the file. I'd like to add the email list all at one time, rather than what appears to be an "add one at a time" method. Any help? And am I understanding the certificate security feature correctly?
    Ken

    Hi George,
    Thanks for a quick response.
    1, create PDF,
    2, exchange Digital ID
    3, encrypt PDF
    4, send the file to recipients
    Correct?
    But I am missing something between or details. I don't know where I am doing wrong..
    When I send the encrypted file, some can open and some people can not. Or print is still allowed and file was not completely secured.
    From the point of creating Digital ID, I would like to know how everyone does it in detail.
    Thank you.

  • Secure PDF using certificate

    Hi All,
    I'm developing a secure PDF using certificate.
    When I open the PDF I get acrobat security saying " A digital ID was used to encrypt this document but no digital ID is present to decrypt it.Make sure your digital ID is properly installed or contact the document author. "
    Any help in resolving this issue is appreciated?

    I have the exact same problem with the following exception:
    I encrypted a portfolio with a public key for a committee, including myself, using our public keys to allow just us to be able to open the portfolio. This worked as it should with Acrobat 9.4.1 and Reader 9.4.1.
    When I updated to Adobe Reader X, I got the infamous
    "Acrobat Security
    A digital ID was used to encrypt this document but no digital ID is present to decrypt it. Make sure your digital ID is properly installed or contact the document author" message.
    On this same computer I can open the portfolio with Acrobat 9.4.1 and it doesn't prompt me for a password. When I open the same portfolio with Adobe Reader X, it asks for the password and gives the message.
    When I upgraded to Reader X, I completely  removed Reader 9 prior to loading Reader X. After a successful upgrade, I set my preferences to match what I had with Reader 9. Next, I re-established my security settings as follows:
    1) Edit>Protection>Security Settings - then set the same private key as before, and
    2) Edit>Protection>Manage Trusted Identities - then set the same public keys as before.
    It should have worked, right?

  • Adobe Reader Crashes while opening Secure PDF Documents

    Hi,
    I have Adobe Reader 8.1.2. Up until today, i was able to open secure PDF documents without any issue. Suddenly, it started to give me errors, saying "Adobe Reader has encountered a problem and it needs to close. I have to tell Microsoft" and so on...
    I tried re-installing 8.1.0, secure documents opened a few times and then the same problem returned. I can open normal PDF documents but the problem is with the secure ones.
    Rebooting, re-installing again didn't help.
    What could be the issue and how to solve it? I have Trend Micro Antivirus s/w but i always had them all these days and everything was fine.
    Thanks
    anand

    Hi,
    Can someone help me on this please?
    I have tried removing Adobe Reader, re-install it but doesn't help. Secure documents do open sometimes but fail again. I have even tried removing Adobe Reader using MSI Cleanup Utility, no use.
    The problem seems to be in the imapdb.dll. An error report is generated by Windows XP but it is rather large to fit in here.
    I also Trend Micro Anti-Virus tool and it may have something to do with it is what i feel.
    Any help on how to solve this will be great.
    Thanks
    Kripaludas

  • How to open a link in secure pdf on iphone?

    I got a secure pdf in my e-mail. I've already type in the password and be able to open the pdf. However, what I want to see is in the link in that pdf. I touch the link but cannot open the file. Please advise.

    I cannot copy the link. It's not show up the URL. I have to click on the link on that pdf. I also try on Acrobat Reader App.

  • Digital Editions will NOT open secured PDF

    My PDF is secured with a permissions password, but does not require a password to open.  But when I drag it into the ADE window, the dialogue box says "This version of Digital Editions does not support password-protected documents."  I have ADE 1.7.2 on Windows 7 HP.  Is there a way to open my secured PDF with ADE?

    I have the exact same problem. When will Adobe fix this limitation?

  • Opening an attachment on a secure PDF on android device.

    How can I open an attachment that is attached to a secure PDF on a Android device?

    Are you using Adobe Reader for Android? There is a forum where you can ask that question:
    Adobe Reader for Android

  • ISSUE OPENING SECURE PDF FILE

    Hi
    I am unable to open the link in the secure pdf file after entering the password. It says to double click the link to view the content in it but nothing happens when I double click it . Please help.

    Hold the Control key and click it. It should open in a browser window... or pop up a warning about Reader trying to connect to the internet. Click OK and it should connect.
    If it doesn't, the link is "broken" and there's NOTHING anyone here can do about that. ONLY the author can fix the link.

  • Anyone know how open "secured" pdf's downloaded and saved?

    Adobe X freezes and shows "Not Responding" when attempting to open some saved pdf's.  Noticed that the pdf's which won't open show "Secured" next to the file name in the upper left corner.  These will open while still online, but cannot open the saved file later.  Windows 7.

    An example of a "Secured" pdf can be found at: www.envisionreports.com/XOM/2011/08605JA11E/default.htm?voting=false.  Choose to download the Notice of Annual Meeting file.  It will open while on line.  But when saved to my computer, Adobe X will not open the file.  In the file name field, it indicates "Secured" and "Adobe Reader Not Responding".  Other pdf's that do not show "Secured" open with no problem.  Don't recall this to have been an issue in earlier versions of Adobe Reader.   

  • Reader X Hangs when opening a secured PDF

    Hi all when I open a secure PDF it can take up to 2 minutes to actually open it but this didnt happen when I had Adobe 9. I have tried uninstalling and re installing but this doesnt help at all.
    Any help would be great,
    Thanks

    I've had the same problem since installing AR10 (see my reply post from na6t on 4-5-2011).  Nothing but problems.  I've got a 15 form porfolio about 560k in size and nothing but problems opening it in two different offices using win xp Pro SP3 3ghz/3gb.  It stalls and about half the time it crashes AR10.  This never happened when we were using AR9..
    welcome to the club,,
    Bob

  • Understanding Password vs Certificate security

    Howdy,
    A client is currently using password-protection on all the PDFs on their website. Visitors can download PDFs, print them, copy text, they just can't edit the PDFs. Someone in their organization forgot the password -- rather than retrieving it from someone else in the organization they used a PDF password-removal tool. Now the organization is wondering if they need to step up their efforts since these password removal tools exist.
    Would certificate encryption work in their case where where their site visitors could still view/print/etc. just not edit the PDFs? What if someone inside the organization needs to unlock it for whatever reason? Is it a pain to get them the appropriate certificate with the permissions to edit the PDF? I'm not sure I'm asking all the right questions...
    Thanks!

    In your case you are talking about the 'permissions' restrictions on a PDF, so the file can be opened by everyone but has controls on printing, copying, etc.*
    First thing; password-based permissions settings are not secure at all. It's trivial to remove them, and only Adobe software guarantees to respect them in the first place. They're an illusion of security which tends to convince most people not to bother trying to bypass the restrictions, but if someone wants to it'll take them 30 seconds.
    Certificate-based encryption uses the digital ID of the recipient, not the creator - so it's only going to work if you get the digital ID from each recipient in advance, and cannot be used for public documents on a website. It can also be removed without access to the private key, but it takes a lot more effort to do so.
    Digital rights management (using Adobe ADEP / LiveCycle Rights Management servers) can protect a file against printing and direct copying with no realistic possibility of the protection being removed, but it's extremely expensive.
    However in every case, if a page is visible on screen it can be captured as a screengrab, then re-OCRed to extract text. You can't extract media, scripts and vector objects, but something like a novel is utterly impossible to secure against copying if it's distributed into an uncontrolled space.
    *The 'open file' security on a file is another matter entirely - even password encryption is secure enough to be uncrackable in any real-world scenario, provided you use a complex string to prevent brute-force attacks.

  • How do I Remove password-encryption in a PDF file

    Hello
    Can anyone help me remove the password encryption on a PDF file? I am trying to submit a PDF file to a on demand printer & they di accept the file if it is password-encrypted.
    Thanks

    I have no idea why the printer thinks there is a password? When I opened the security link in Acrobat nothing is selected? So I'm stuck. I also opened the PMD thinking there was some password attached there & I found nothing?

  • Problems with secure PDFs in Preview

    I recently saved and secured a PDF with Adobe Acrobat 9. While the document is secure when I open it with Adobe Acrobat or Reader, there is no security when I open up the same document with Preview... So much for the 256 bit encryption...
    Has anyone else experienced this problem?
    Thanks,
    Barry

    Wow! So much for all the money Adobe put into securing PDFs...
    Thanks for your help.
    Barry

  • Failed Calling A X.509 Certificate Secured Web Service From OSB

    Hi,
    I have wsdl resource, business service and proxy service setup in OSB 11.1.1.6 on Linux. The business service will consume a X.509 certificate secured web service running on a remote server.
    Below is my approach:
    The consumer of the proxy service of OSB signs its saop request header.
    My OSB proxy service authenticates the signature and forward the request to business service.
    The business service signs the outbound soap request header. (To do this I configured the keystore in Security Provider Configuration of my SOA_domain in Enterprise Manager. Also I applied Web Service Policy of Service Client type to the business service.)
    This is not working yet. Not sure if my approach is correct or not?
    Thank you,
    Eric

    I validated the keystore, all the certificates used and the value for keystore.sig.csf.key / value for keystore.recipient.alias. They are all as expected. Restarted the server. Still failed for OSB to invoke the remote secured web service, but worked if only use soapUI to invoke the same remote secured web service directly.
    The error message is:
    General security error (WSSecurityEngine: No crypto property file supplied for decryption); nested exception is org.apache.ws.security.WSSecurityException: General security error (WSSecurityEngine: No crypto property file supplied for decryption)
    In the soap request / reponse message shown in the OSB Test Console, there seems to be two signature sections in the header and encryption section although I tried not to encrypt the soap request. I am using Web Service Client Policy "calpers/wss11_x509_token_with_message_integrity_client_policy_osb" which was created based on "oracle/wss11_x509_token_with_message_protection_client_policy". The difference between the two policies is my policy not to sign nor to encrypt entire body.
    In the "Message Signing Setting" section, I unchecked the "Include Entire Body" and left the three default namespaces under the Header Elements.
    In the "Message Encrypt Setting" section, I unchecked the "Include Entire Body" and also left the one default namespace under the Header Elements.
    I don't know how to attach document here, so i add long saop message here.
         Business Service Testing - BookSec_Biz_Svc_52
         Request Document
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    </soap:Header>
    <soapenv:Body>
    <book:BookRequest xmlns:book="http://www.dortman.com/books/BookService">
    <book:bookId>10</book:bookId>
    <book:bookTitle>eric</book:bookTitle>
    <book:bookAuthor>Z</book:bookAuthor>
    </book:BookRequest>
    </soapenv:Body>
    </soapenv:Envelope>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <wsu:Timestamp wsu:Id="Timestamp-eEud1RcUOPcnV0fDqd6gZQ22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <wsu:Created>2013-03-14T18:10:00Z</wsu:Created>
    <wsu:Expires>2013-03-14T18:15:00Z</wsu:Expires>
    </wsu:Timestamp>
    <wsse:BinarySecurityToken ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" wsu:Id="BST-VnzMtSwHMI8THKi2hhG2SQ22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    MIICazCCAdSgAwIBAgIEUTY65zANBgkqhkiG9w0BAQUFADB6MQswCQYDVQQGEwJVUzERMA8GA1UECBMITmV3IFlvcmsxEzARBgNVBAcTCk1ldHJvcG9saXMxFjAUBgNVBAoTDUp1c3RpY2UgTGVhZ2UxFjAUBgNVBAsTDUp1c3RpYyBMZWFndWUxEzARBgNVBAMTCkNsYXJrIEtlbnQwHhcNMTMwMzA1MTgzNTE5WhcNMTMwNjAzMTgzNTE5WjB6MQswCQYDVQQGEwJVUzERMA8GA1UECBMITmV3IFlvcmsxEzARBgNVBAcTCk1ldHJvcG9saXMxFjAUBgNVBAoTDUp1c3RpY2UgTGVhZ2UxFjAUBgNVBAsTDUp1c3RpYyBMZWFndWUxEzARBgNVBAMTCkNsYXJrIEtlbnQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJhF0cMUwB/EjAyIOy9Cq8KCDqTXvlnlvMGq6LEhiGOtrATYy+JnHURcPUeusi65Ua3bE7JACWhHJ0fYEl7NtxPPSN3Q1RovkWGQ6I5O2XuEyMHg3MISh2CHhnkGSR+W6riDSUoB0ZC0KTgu14OTwqo54JSY/ugQszY7QC9DAuabAgMBAAEwDQYJKoZIhvcNAQEFBQADgYEAWeQ6LjMo12bY65GmnrmLdbRNm95RkL6gJCKa9pyUaMfvaIqKpmMQW8RM+eB90CR5DrM8oO2+8uKcqTt/pGNRYi2UJh2X0CdmyQQTmf3mCfgoZ597VTl+k3mKHKeeST7ZwAyBRL2jI0VisopFHpUhIwABoDgwOMpLcCF974AZ2rA=
    </wsse:BinarySecurityToken>
    *<dsig:Signature* Id="XSIG-oISn2AADumTdR86sONuz8g22" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
    <dsig:SignedInfo>
    <dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    <dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"/>
    <dsig:Reference URI="#Timestamp-eEud1RcUOPcnV0fDqd6gZQ22">
    <dsig:Transforms>
    <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    </dsig:Transforms>
    <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
    <dsig:DigestValue>3LQ1IpQR3rKHvP6Ov/m9ZRoecZM=</dsig:DigestValue>
    </dsig:Reference>
    </dsig:SignedInfo>
    <dsig:SignatureValue>X2BUn9TLL26Ay9A3HGEn/mnGCCE=</dsig:SignatureValue>
    <dsig:KeyInfo>
    <wsse:SecurityTokenReference>
    <wsse:Reference URI="#EK-h7saqC1VyBKZw2n1IHz8GQ22" ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey"/>
    </wsse:SecurityTokenReference>
    </dsig:KeyInfo>
    +*</dsig:Signature>*+
    *<dsig:Signature* xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
    <dsig:SignedInfo>
    <dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    <dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
    <dsig:Reference URI="#BST-VnzMtSwHMI8THKi2hhG2SQ22">
    <dsig:Transforms>
    <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    </dsig:Transforms>
    <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
    <dsig:DigestValue>dau9qjB2lxIvlaoDIHuWVHqjulI=</dsig:DigestValue>
    </dsig:Reference>
    <dsig:Reference URI="#STR-QC3ZDBRwsXv8unEWVns9rQ22">
    <dsig:Transforms>
    <dsig:Transform Algorithm="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform">
    <wsse:TransformationParameters>
    <dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    </wsse:TransformationParameters>
    </dsig:Transform>
    </dsig:Transforms>
    <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
    <dsig:DigestValue>nPO9mKSC9cMg2fEkGZI+ujy5O1Q=</dsig:DigestValue>
    </dsig:Reference>
    <dsig:Reference URI="#XSIG-oISn2AADumTdR86sONuz8g22">
    <dsig:Transforms>
    <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    </dsig:Transforms>
    <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
    <dsig:DigestValue>qXkW/ZFFNc8Bu0VL9eF6c4np7IA=</dsig:DigestValue>
    </dsig:Reference>
    </dsig:SignedInfo>
    <dsig:SignatureValue>
    MuHCTh5cW8TiVKtkWFl+Of2EFAiHwuPTR7J9b4/n2KZtPy2OCrgi1lBpuzhFKLhoBxYNOK8TMOa/3b223Vv+CQUfUP7z0YVj5Ck7QETYngaQlS07KulnstJjsAgHBV8Zk3A0EafuWF2c3t5wBzEkgEC99v0EdY3mRiCzt7vh2qs=
    </dsig:SignatureValue>
    <dsig:KeyInfo Id="KeyInfo-0LT1QavoIVXOHesZfrxTwg22">
    <wsse:SecurityTokenReference>
    <wsse:Reference URI="#BST-VnzMtSwHMI8THKi2hhG2SQ22" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
    </wsse:SecurityTokenReference>
    </dsig:KeyInfo>
    +*</dsig:Signature>*+
    *<xenc:EncryptedKey* Id="EK-h7saqC1VyBKZw2n1IHz8GQ22" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
    <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p">
    <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"/>
    </xenc:EncryptionMethod>
    <dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
    <wsse:SecurityTokenReference wsu:Id="STR-QC3ZDBRwsXv8unEWVns9rQ22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">q9Z9yPxvNw4CvSLQNI4rxVlSF+w=</wsse:KeyIdentifier>
    </wsse:SecurityTokenReference>
    </dsig:KeyInfo>
    <xenc:CipherData>
    <xenc:CipherValue xmime:contentType="application/octet-stream" xmlns:xmime="http://www.w3.org/2005/05/xmlmime">
    Tgdhxy6wMJBBrw23iq1GLCm0TYKBXSVQvBcN+7TXdXL6FPSjhcbfXqtoz7wzirbSwUZuu+DrYuWs
    0BjRXqw3auUSCMlkm4IoT1ag3wFQQ/PEbB8HNlYhW3gp/At3toTw+k5p9wOUd4BMFAiXyeHQ8+dQ
    8JUiohXhiHErTDn6fFQ=
    </xenc:CipherValue>
    </xenc:CipherData>
    </xenc:EncryptedKey>
    </wsse:Security>
    </soap:Header>
    <soapenv:Body>
    <book:BookRequest xmlns:book="http://www.dortman.com/books/BookService">
    <book:bookId>10</book:bookId>
    <book:bookTitle>eric</book:bookTitle>
    <book:bookAuthor>Z</book:bookAuthor>
    </book:BookRequest>
    </soapenv:Body>
    </soapenv:Envelope>
         Response Document
    The invocation resulted in an error: Internal Server Error.
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
    <soapenv:Fault>
    <faultcode>soapenv:Client</faultcode>
    <faultstring xmlns:lang="en">
    General security error (WSSecurityEngine: No crypto property file supplied for decryption); nested exception is org.apache.ws.security.WSSecurityException: General security error (WSSecurityEngine: No crypto property file supplied for decryption) </faultstring>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>
         Response Metadata
    <con:metadata xmlns:con="http://www.bea.com/wli/sb/test/config">
    <tran:headers xsi:type="http:HttpResponseHeaders" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <tran:user-header name="Accept" value="text/xml"/>
    <tran:user-header name="Expires" value="Thu, 14 Mar 2013 18:10:01 GMT"/>
    <tran:user-header name="SOAPAction" value="&quot;&quot;"/>
    <http:Cache-Control>max-age=0</http:Cache-Control>
    <http:Connection>close</http:Connection>
    <http:Content-Type>text/xml; charset=UTF-8</http:Content-Type>
    <http:Date>Thu, 14 Mar 2013 18:10:01 GMT</http:Date>
    <http:Server>Apache</http:Server>
    <http:Transfer-Encoding>chunked</http:Transfer-Encoding>
    </tran:headers>
    <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">2</tran:response-code>
    <tran:response-message xmlns:tran="http://www.bea.com/wli/sb/transports">Internal Server Error</tran:response-message>
    <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">UTF-8</tran:encoding>
    <http:http-response-code xmlns:http="http://www.bea.com/wli/sb/transports/http">500</http:http-response-code>
    </con:metadata>

  • Secure pdf viewing on ipad

    How can i view a secure pdf on an ipad?

    The Adobe Reader for iPad supports viewing of encrypted and LCRM protected PDF's. There are several other "secure" or "protection" schemes created by third parties, and we don't have the ability to open those documents. Have you tried your secure PDF in the Adobe Reader (available for free in the App Store).

Maybe you are looking for