... I'm only mildly concerned about
the keyring name, as we use a totally different name associated with
SMP/E, not with Java. That keyring works fine today.
If you're already downloading securely, then you can continue to use
your same keyring. My example in the article was simply that, an
example, which uses the default Java truststore instead of a security
manager (RACF) keyring:
<CLIENT
downloadmethod=”https”
downloadkeyring=”javatruststore”
javahome="/usr/lpp/java/J6.0"
>
</CLIENT>
I call this the "Fast Path" because for someone that is not already
downloading securely, then using HTTPS with the Java truststore is the
quickest and simplest choice because you don't need to mess around with
keyrings or a security manager product at all.
If anyone is interested, more details can be found here:
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r1.gim3000/dsetups.htm
Kurt Quackenbush -- IBM, SMP/E Development
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
