Oracle Access Manager 11g and MD5 Algorithm Statement of Direction
(Doc ID 2324412.1)
Last updated on JANUARY 24, 2019
Applies to:COREid Access - Version 10.1.4.3.0 and later
Oracle Access Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Starting with the April Critical Patch Update releases, (April 18, 2017), all JRE versions will treat JARs signed with MD5 as unsigned.
Newer versions of Java now require all JAR files to be signed with a valid code-signing key, and starting with Java 7 Update 51 and up, unsigned or self-signed applications are blocked from running. For more information refer to Oracle JRE will no longer trust MD5-signed code by default .
This note is to proved OAM Support analyst a starting point when dealing with issue related to this change.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Oracle JAVA/JRE will no longer trust MD5-signed code|
|OAM Support Stance ...|
|This effects the OAM 11g product in the following Areas ...|
Coherence (Admin Server starting)
|Existing OAM KM notes that contain work around|