More

IBM WebSphere HTTP Server

 

I.  Download Intermediate and Cross Root CA files from Costumer Panel (edit it with Notepad. Other editors may add additional characters). Downloaded files save as intermediate.txt and crossroot.txt.

 
II. Install the Intermediate CA
1. Start the key management utility (iKeyman)
2. Open the key database file that was used to create the certificate request.
3. Enter the password, and then click OK.
4. Select Signer Certificates and then click Add.
5. Click Data type, and select a data type, such as Base64-encoded ASCII data. This data type must match the data type of the importing certificate.
6. Browse the intermediate.txt file you created and click OK.
7. Enter a label for the importing certificate and click OK.
8. The Signer Certificates field displays the label of the signer certificate you added.
 
III. Install the Cross Root CA
1. Start the key management utility (iKeyman)
2. Open the key database file that was used to create the certificate request.
3. Enter the password, and then click OK.
4. Select Signer Certificates and then click Add.
5. Click Data type, and select a data type, such as Base64-encoded ASCII data. This data type must match the data type of the importing certificate.
6. Browse the crossroot.txt file you created and click OK.
7. Enter a label for the importing certificate and click OK.
8. The Signer Certificates field displays the label of the signer certificate you added.
 
IV. Download your certificate and follow the instructions received in e-mail. Copy and paste it into a text file and save as ssl.arm.
 
V. Install the Certificate
 
iKeyman GUI (graphical user interface):
1. Start the iKeyman using either the gsk7ikm command (UNIX) or the strmqikm command (Windows).
Note: To use the iKeyman GUI, be sure that your machine can run the X Windows system.
2. From the Key Database File menu choose Open. Click Key database type, and select CMS.
3. Click Browse to navigate to the directory containing the key database file to which you want to add the certificate and click Open.
4. Type the password you set when you created the key database and then click OK.
5. Select the Personal Certificates view and click Receive.
6. Select the data type of the new SSL certificate. Base64-encoded ASCII for a .arm file.
7. Click Browse to select the name and location of the certificate file name and click OK.
 
iKeycmd (command line interface):
 
UNIX command line:
+ gsk7cmd -cert -receive -file filename -db filename -pw password -format ascii
 
Windows command line:
+ runmqckm -cert -receive -file filename -db filename -pw password -format ascii
 
where:
+ -file filename is the fully qualified file name of the file containing the personal certificate.
+ -db filename is the fully qualified file name of a CMS key database.
+ -pw password is the password for the CMS key database.
+ -format ascii is the format of the certificate. The value can be ascii for Base64-encoded ASCII or binary for Binary DER data. The default is ascii.
 
VI. Transferring certificates
To extract an SSL certificate from a key database file and store it in a CA key ring file you must:
 
iKeyman GUI (graphical user interface):
1. Start the iKeyman using either the gsk7ikm command (UNIX) or the strmqikm command (Windows).
2. From the Key Database File menu choose Open. Click Key database type, and select CMS.
3. Click Browse to navigate to the directory containing the key database file to which you want to add the certificate and click Open.
4. Type the password you set when you created the key database and then click OK.
5. Select Signer Certificates in the Key database content field, and then select the certificate you want to extract. Next click Extract.
6. Select the data type of the new SSL certificate. Base64-encoded ASCII for a .arm file.
7. Click Browse to select the name and location of the certificate file name and click OK. The certificate is written to the file you specified.
 
iKeycmd (command line interface):
 
UNIX command line:
+ gsk7cmd -cert -extract -db filename -pw password -label label -target filename -format ascii
 
Windows command line:
+ runmqckm -cert -extract -db filename -pw i -label label -target filename -format ascii
 
where:
+ -db filename is the fully qualified pathname of a CMS key database.
+ -pw password is the password for the CMS key database.
+ -label label is the label attached to the certificate.
+ -target filename is the name of the destination file.
+ -format ascii is the format of the certificate. The value can be ascii for Base64-encoded ASCII or binary for Binary DER data. The default is ascii.
 

Other questions from SSL Installation

Other categories

cyber_Folks S.A. – Cookie settings

Do you like good cookies? We too! Some cookies are required for the website to function properly. Also accept additional cookies related to service performance, social networking and marketing. Cookies are also used to personalize ads. Thanks to them, you will get the best experience of our website, which we are constantly improving. The consent granted voluntarily may be withdrawn or modified at any time. More information about the cookies used can be found in our privacy policy. If you prefer to specify your preferences precisely - see the types of cookies below.

Functional (always active)

These are cookies that are necessary for the website to function. The website will not function fully properly without accepting these types of cookies. Example: A cookie that saves your consent or objection is needed so that we know if we have your consent for certain actions on the website, they will also allow you to log in to the Customer Panel, place an order or contact us via chat.

Analytical and performance

They will make it possible to collect information on how to use the website. These files will allow us to count visits and traffic sources to our site, so we can measure and improve its performance, as well as find out which pages are the most and least popular, and understand how visitors navigate our site. They help us analyze website performance and collect synthetic information. Example: We can make heatmaps, so we know which content is readable and which is not, and this allows for better website design. Thanks to them, we can also see which blog entries were read more often and which less often, which allows us to develop more interesting content. The main tool we use is Google Analytics.

Social

It is social platform cookies that will enable you to be associated with your social media accounts. You can share content from our website there. Social network files (from third parties, such as Facebook) collect information to provide personalized advertising content. For example: Ads on your social media are better suited to you and you reduce the chance of seeing excess ads for already purchased services or products.

Marketing

These are files related to the operation of marketing automation systems and ad accountability. Thanks to them, we limit, for example, the number of views of a given advertisement. They also allow us to perform comparative tests, thanks to which we constantly improve the operation of our website. By testing multiple page layouts, it is easier to get one that provides the best readability for users. Communication also becomes more personalized. For example, we may give you an article on how to find a domain name when we see that you are looking for a domain and it is difficult for you to find a suitable name. We can also, for example, show you a hint about logging in, if we see several unsuccessful attempts in a row. Based on the information from these cookies and activity on other websites, your interest profile is built. We mainly use the Google and Facebook advertising network.