Note the alias of your personal certificate (highlighted in bold above), you will need that later. You can see that both the certificate and the signing authority have both been imported into the keystore. Import command completed: 2 entries successfully imported, 0 entries failed or ca-celled You will see output similar to the following: Entry for alias 0cn=cics 2048 sample certification authority, ou=cics test department, o=leading edge cics enterprise, l=gotham city, st=xanadu, c=us successfully imported.Įntry for alias attlsring2c-2048-certificate successfully imported. Advice online says that you should set this to be the same as certificate_password however I cannot see why this would be necessary. Keystore_password a new password for this keystore. Drop into a command shell and issue the following command to generate the keystore: C:\Users\IBM_ADMIN\Documents\IBM\HermesTest\jmx files\certificates>keytool -importkeystore -srckeystore certificate.P12 -srcstoretype PKCS12 -srcstorepass certificate_password -keystore mystore.keystore -storepass keystore_passwordĬertificate.P12 is your personal certificate file that you extracted from RACFĬertificate_password is the password for the certificate There are 3 stages to complete:įirst, the exported certificate needs to be imported into a java keystore so it can be read by java.Ĭopy the *.p12 file (and the certificate authority. This article assumes that RACF and CICS are configured and that the private key along with the certificate signing authority have been exported from RACF and are available on your machine. In turn, this configuration allows CICS to map the certificate to a RACF user ID and run the transaction as that user. This will allow each request to be signed and encrypted. In this article we discuss how to configure JMeter to use client side SSL to authenticate each request.
0 Comments
Leave a Reply. |