Technical data

SSL Certificate Validation
Administration Guide 14-75
If you only have the end entity certificate, you can also tell whether it is old or
new by looking at the Issuer DN.
3. Update the environment scripts for WebLogic Server to include the JAR files for
the patch.
l On Windows NT, edit the following files:
%WL_HOME%\server\bin\setWLSEnv.cmd
%WL_HOME%\server\bin\startWLS.cmd
%WL_HOME%\server\bin\startNodeManager.cmd
Add the following to the CLASSPATH before the weblogic_sp.jar:
%WL_HOME%\server\lib\CR090101_610sp4_webservice.jar;
%WL_HOME%\server\lib\CR090101_610sp4_.jar;
l On UNIX, edit the following files:
$WL_HOME/server/bin/setWLSEnv.sh
$WL_HOME/server/bin/startWLS.sh
$WL_HOME/server/bin/startNodeManager.sh
Add the following to the CLASSPATH before the weblogic_sp.jar:
$WL_HOME/server/lib/CR090101_610sp4_webservice.jar;
$WL_HOME/lib/CR090101_610sp4.jar;
4. Using the files from the patch, update the certificates, private keys, and keystores
in existing domains.
Older unpatched applications will not trust the new demo CA certificates that are
installed by this patch. For example, a client that is still trusting the old demo CA
certificate, will reject a server that has a new demo certificate chain. Resolve this
problem by updating the client's trusted CA list to include the new demo CA supplied
by this patch.