You can configure CA CSM to use HTTPS instead of HTTP for user access manually using an external security manager, for example, CA Top Secret for z/OS, CA ACF2 for z/OS, or IBM RACF to store digital certificates.
Follow these steps:
We recommend you generate the certificate using the RSA algorithm. The recommended certificate alias is tomcat.
<!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
<Connector port="30308" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
SSLEnabled="true"
algorithm="IbmX509"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS"
sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"
keystoreType="JCERACFKS"
keystoreFile="safkeyring://KEY_RING_OWNER/KEY_RING_NAME"
sslImplementationName="com.ca.sslsocket.CASSLImplementation" />
Example: keystoreFile="safkeyring://MSMSERV/CSMKEYRING"
Note: When the Apache Tomcat server is starting up, the following message may appear in the output:
WARNING: configured file: ./path/safkeyring://KEY_RING_OWNER/KEY_RING_NAME. does not exist.
You can ignore this message.
Note: When you access the HTTPS URL from your browser for the first time, you may be prompted to confirm that you trust the certificate.
Note: For more information, see documentation for the Apache Tomcat 7.0 Servlet/JSP Container.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|