Tim, I hoped to avoid this discussion but I guess it's inevitable. In the
process of validating everything after the upgrade to 12.1.0.5 I noticed that
the WL admin console wasn't available, returning the classic "There is a
problem with this website’s security certificate" error. Totally my fault as I
hadn't been paying attention to this. I had already done a round of increasing
the key length and adding self-signed certs to the 11g consoles but from I've
been able to find the same kind of commands don't work for the WL console.
Reading various docs I saw solutions of making adjustments in the WL console,
which obviously I can't do at this point, along with changes directly to
various .properties files and/or .sh startup scripts. I figured there had to
be a better solution, such as just applying the latest patches. When PSU 13 on
WL didn't resolve the issue I raised an SR and now I'm stuck with the whole JDK
route.
Regards,
Dave
-----Original Message-----
From: timseanhall@xxxxxxxxx [mailto:timseanhall@xxxxxxxxx] On Behalf Of Tim Hall
Sent: Wednesday, February 10, 2016 4:07 AM
To: Timur Akhmadeev
Cc: Herring, David; oracle-l@xxxxxxxxxxxxx
Subject: Re: jdk16 to jdk17 frustration
Question: What was the original problem with WL Admin. I run 12.1.0.5 and all I
needed to do was recreate the certificate to get round that annoying "weak
ephemeral diffie-hellman public key" error. I know one of the options was to
upgrade a bunch of stuff, but screw that. :)
Cheers
Tim...
