使用iTextPDF签名PDF时遇Illegal keysize错误（BouncyCastleProvider）

Ah, that classic Illegal keysize error—this almost always boils down to Java's default cryptographic restrictions getting in your way. Let me break down why this is happening and how to fix it:

The Root Cause #

Oracle JDK (and some OpenJDK distributions) ship with default limits on the key lengths allowed for strong encryption algorithms. When your .p12 file contains a key longer than these defaults (e.g., RSA keys larger than 2048 bits, or AES keys over 128 bits), Java blocks the operation and throws this error. Your earlier KeyStore setup probably used keys that fit within the default limits, which is why it worked fine.

Step-by-Step Solutions #

1. For Java 8 or Earlier #

You'll need to replace the default JCE (Java Cryptography Extension) policy files with the unlimited strength versions:

• Navigate to your JDK's jre/lib/security directory
• Grab the local_policy.jar and US_export_policy.jar files for your Java version (these are included in some OpenJDK builds like AdoptOpenJDK, or available from official sources)
• Replace the existing files in the security folder (make a backup first just in case)
• Note: Some OpenJDK 8 distributions already enable unlimited crypto by default—you can skip this if you're using one of those.

2. For Java 9+ #

Java 9 and later removed the separate JCE policy files. Instead, you just need to enable unlimited crypto via:

• JVM Argument: Add this when starting your application:

  -Dcrypto.policy=unlimited
  

• In-Code Setting: Add this line before loading your KeyStore to set it programmatically:

  Security.setProperty("crypto.policy", "unlimited");
  

3. Check BouncyCastle Setup #

• Make sure you're using the latest version of BouncyCastle Provider (e.g., bcprov-jdk15on for modern JDKs). Old versions can have compatibility issues with crypto restrictions.
• Try removing the explicit provider name when loading the KeyStore—let Java auto-select the right provider instead:

  KeyStore ks = KeyStore.getInstance("PKCS12"); // Omit the second provider argument
  

  Sometimes forcing BouncyCastle here can trigger unnecessary permission checks.

4. Verify Your Key's Length #

Quickly check the key size in your .p12 file to confirm it's exceeding defaults:

KeyStore.PrivateKeyEntry entry = (KeyStore.PrivateKeyEntry) ks.getEntry(alias, new KeyStore.PasswordProtection(password.toCharArray()));
PrivateKey privateKey = entry.getPrivateKey();
if (privateKey instanceof RSAPrivateKey) {
    RSAPrivateKey rsaKey = (RSAPrivateKey) privateKey;
    System.out.println("Key length: " + rsaKey.getModulus().bitLength());
}

If it's over 2048 bits (or 128 bits for symmetric keys), that's definitely the trigger for the error.

Final Notes #

After making these changes, restart your application and test the signature again. If you still run into issues, double-check that you've applied the policy changes to the correct JDK/JRE instance your application is using—it's easy to accidentally modify the wrong one!

内容的提问来源于stack exchange，提问作者Kegan.rodhe