PDF Security & Access Issues

How to Encrypt PDFs with FIPS Certificates for Recipients

Chanuka GeekiyanageChanuka Geekiyanage Nov 3, 2026 869 views

Question details

Users need to encrypt PDF documents using FIPS certificates so specific recipients can open them, but face access issues when only the public certificate is shared.

How to Encrypt PDFs with FIPS Certificates for Recipients
Product
PDF
Device & OS
not provided
Scenario
Encrypting a PDF document in FIPS 140 mode for secure distribution to specific recipients.
Observed behavior
Recipients are unable to open the encrypted PDF if they only receive the public certificate and lack the corresponding private key on their system.
Before you start

Verify that your recipient has successfully generated a digital ID and has their private key installed in their local certificate store before you attempt to send an encrypted file.

Solution 1Recommended

Distribute and Verify Certificate Keys for PDF Encryption

Follow this standard public-key infrastructure (PKI) workflow to ensure recipients can successfully decrypt and open the FIPS-encrypted PDF.

Certificate-based PDF encryption relies on a cryptographic key pair. The sender encrypts the document using the recipient's public key, and the recipient decrypts it using their unique private key.

Sending a public key (.cer) to a recipient who does not already possess the private key will not grant them access.

1
Obtain the public key

Request the recipient's public-key certificate (usually a .cer file). The sender must import this file into their trusted identities list within their PDF software.

2
Encrypt the document

Open the PDF, choose the certificate encryption option, and add the recipient's public key to the list of authorized users.

3
Ensure private key availability

The recipient must verify that the corresponding private key is securely installed in their operating system's digital ID store (such as the Windows Certificate Store or macOS Keychain).

4
Open the encrypted file

Send the encrypted PDF. When the recipient opens the file, their PDF reader will automatically query the system for the installed private key to verify their identity and unlock the document.

Distribute and Verify Certificate Keys for PDF Encryption
Important Security Rule: Never share or transmit a private key. Only the public key (.cer) is meant to be shared with others. If the recipient generated the initial certificate request, their private key should already be safely stored on their device.
Secure PDF Management

Encrypt and Secure PDFs easily with WPS Office

WPS Office provides robust PDF security tools, allowing you to easily encrypt documents, restrict permissions, and manage secure file sharing without complicated setups.

  1. 1. Open your PDF: Launch WPS Office and open the PDF document you want to secure.
  2. 2. Access protection tools: Navigate to the 'Protect' tab located on the top ribbon menu.
  3. 3. Apply encryption: Select 'Encrypt' to apply password protection or certificate security to your document.
  4. 4. Save and share: Configure your security preferences, save the newly encrypted file, and securely distribute it to your recipients.
Easy-to-use password and certificate-based encryptionSeamless compatibility with standard Microsoft Office and PDF security protocolsComprehensive PDF editing, conversion, and management features
microsoft office alternative - wps office

Frequently Asked Questions

Why can't my recipient open the PDF if I sent them the .cer certificate?

A .cer file only contains the public key, which is strictly used for encrypting the document. To open and decrypt the file, the recipient must have the corresponding private key installed on their system.

What does FIPS 140 mode mean in PDF encryption?

FIPS 140 is a United States government security standard for cryptographic modules. When FIPS mode is enabled, the PDF software strictly uses approved, high-security encryption algorithms and requires valid certificate handling.

How does a recipient obtain their private key?

The private key is generated simultaneously with the public key when the user creates a digital ID. It remains securely stored on the device, token, or smart card of the person who originally created the digital ID.