Difference between revisions of "Java encryption key - setting unlimited length"
Jump to navigation
Jump to search
(Created page with "=Overview= Releases of the Oracle Java Runtime Environment (JRE) prior to 1.8.0_151 require a change to their default security policy configuration to support the 256-bit AES...") |
|||
| Line 4: | Line 4: | ||
If an <strong>Encryption Failed - Illegal key size or default parameters</strong> error is reported, change to a different Java implementation such as [https://aws.amazon.com/corretto/ Amazon Corretto 8], or follow the procedure below to modify the Oracle Java security policy to support encryption keys of unlimited length. | If an <strong>Encryption Failed - Illegal key size or default parameters</strong> error is reported, change to a different Java implementation such as [https://aws.amazon.com/corretto/ Amazon Corretto 8], or follow the procedure below to modify the Oracle Java security policy to support encryption keys of unlimited length. | ||
| − | = | + | ====1. Shutdown the Java web application server - e.g. Tomcat==== |
| + | ====2. In JAVA_HOME, search for the file java.security==== | ||
Revision as of 02:02, 13 October 2020
Overview
Releases of the Oracle Java Runtime Environment (JRE) prior to 1.8.0_151 require a change to their default security policy configuration to support the 256-bit AES encryption used by the Fusion products for sensitive data.
If an Encryption Failed - Illegal key size or default parameters error is reported, change to a different Java implementation such as Amazon Corretto 8, or follow the procedure below to modify the Oracle Java security policy to support encryption keys of unlimited length.
