06.05.2013 Views

The eG Installation Guide - eG Innovations

The eG Installation Guide - eG Innovations

The eG Installation Guide - eG Innovations

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Installing and Configuring on Unix<br />

<strong>The</strong> text in Bold in the above command line indicates those inputs that can change according to<br />

the requirements of your environment. <strong>The</strong>se inputs have been described below:<br />

-alias : the alias name of the certificate being extracted; make sure that you provide the same alias<br />

name that you provided while generating the keystore file (see Section 2.2.1 of this document).<br />

-keypass : the password used to protect the key that was generated; make sure that you provide<br />

the same password that you provided while generating the keystore file (see Section 2.2.1 of this document).<br />

Also, note that -storepass and -keypass should be the same.<br />

-keystore : Provide the name of the keystore file in which the key has been stored; specify the<br />

same file name that you used to store the key (see Section 2.2.1 of this document).<br />

-file : Specify the full path to and the name of the certificate file (.cer) to which the certificate<br />

has to be exported<br />

3. Once the keytool command successfully executes, the certificate file will be created.<br />

2.2.3 Requesting a Certificate Authority for a Valid Certificate<br />

Self-signed certificates are useful in environments where 'security' is not a priority. In highly secure<br />

environments, especially where the <strong>eG</strong> manager is to be frequently accessed via the public internet,<br />

using a self-signed certificate may not be preferred. In such a case, you can request for a valid<br />

certificate from a certificate authority. <strong>The</strong> procedure for this is as follows:<br />

Login to the <strong>eG</strong> manager and go to the shell prompt.<br />

Execute the following commands one after another:<br />

cd $JAVA_HOME/bin<br />

keytool -certreq -alias egitlab1 -file -keypass mykey -keystore<br />

.keystore –storepass mykey<br />

<strong>The</strong> text in Bold in the above command line indicates those inputs that can change according to<br />

the requirements of your environment. <strong>The</strong>se inputs have been described below:<br />

-alias : the alias name of the certificate being requested; make sure that you provide the same alias<br />

name that you provided while generating the keystore file (see Section 2.2.1 of this document).<br />

-file : Provide a name for the text file to which the certificate request will be saved.<br />

-keypass : the password used to protect the key that was generated; make sure that you provide<br />

the same password that you provided while generating the keystore file (see Section 2.2.1 of this document).<br />

Also, note that -storepass and -keypass should be the same.<br />

-keystore : Provide the name of the keystore file in which the key has been stored; specify the<br />

same file name that you used to store the key (see Section 2.2.1 of this document).<br />

If this command executes successfully, then a certificate will be issued by a certifying authority.<br />

38

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!