Difference between revisions of "Accessing KHIKA Gui"

From khika
Jump to navigation Jump to search
(Created page with "== Login == In this section we assume that your VM is ready. You can login into the GUI using the Web Browser (Google Chrome) for further configuration of KHIKA. ''Note: KHIK...")
 
Line 7: Line 7:
  
 
Note that the certificate for the web server is self-signed and hence the browse will warn you at this. You may ignore this warning and proceed.
 
Note that the certificate for the web server is self-signed and hence the browse will warn you at this. You may ignore this warning and proceed.
 +
  
 
login1
 
login1
 +
 +
 +
Click Advanced to proceed to get below message
 +
 +
 +
login2
 +
 +
 +
Following landing page for user login appears.
 +
 +
 +
login3
 +
 +
 +
If you wish to install your own certificate, please perform below steps
 +
*Login to the appliance using ‘khika’ user using your favourite ssh client
 +
*cd /opt/KHIKA/kibana/config
 +
*Open kibana.yml in ‘vi’ editor
 +
*Locate section ‘server.ssl.enabled’. It looks like below
 +
 +
 +
login4
 +
 +
 +
The default self-signed certificates are installed in following directory: /opt/KHIKA/3rdpartyUnix/Apache24/conf/
 +
 +
Note that KHIKA supports PEM-Format SSL certificates. Please refer to the documentation of your certificate vendor to convert your certificates into the PEM format, if they are in any other format.
 +
 +
*After you have the .crt (i.e. the certificate) and the .key (i.e. private key) files, copy them in /opt/KHIKA/3rdpartyUnix/Apache24/conf/ directory.
 +
*Change the filenames (and directory paths if you have copied the certificate and key anywhere else) if required in kibana.yml file
 +
*Make sure that the ‘server.ssl.certificate’ stanza points to the full path of the certificate and ‘server.ssl.key’ stanza points to the full path of the private keys.
 +
*After editing and saving kibana.yml, come to the command prompt. Enter cd /opt/KHIKA and fire command “./khika_appserver.sh stop”
 +
*Wait for some time (2 to 3 minutes)
 +
*Fire command ‘./khika_appserver.sh start’ from /opt/KHIKA directory
 +
*Connect using the fresh session of the browser
 +
*Login using default credentials (i.e. username = admin, password = admin).

Revision as of 09:15, 4 June 2019

Login

In this section we assume that your VM is ready. You can login into the GUI using the Web Browser (Google Chrome) for further configuration of KHIKA. Note: KHIKA does not support any browser apart from Google Chrome.

Open the Google Chrome browser and enter IP address of KHIKA server. The URL is in the format : https://IP_address_of_KHIKA_App_Server

Note that the certificate for the web server is self-signed and hence the browse will warn you at this. You may ignore this warning and proceed.


login1


Click Advanced to proceed to get below message


login2


Following landing page for user login appears.


login3


If you wish to install your own certificate, please perform below steps

  • Login to the appliance using ‘khika’ user using your favourite ssh client
  • cd /opt/KHIKA/kibana/config
  • Open kibana.yml in ‘vi’ editor
  • Locate section ‘server.ssl.enabled’. It looks like below


login4


The default self-signed certificates are installed in following directory: /opt/KHIKA/3rdpartyUnix/Apache24/conf/

Note that KHIKA supports PEM-Format SSL certificates. Please refer to the documentation of your certificate vendor to convert your certificates into the PEM format, if they are in any other format.

  • After you have the .crt (i.e. the certificate) and the .key (i.e. private key) files, copy them in /opt/KHIKA/3rdpartyUnix/Apache24/conf/ directory.
  • Change the filenames (and directory paths if you have copied the certificate and key anywhere else) if required in kibana.yml file
  • Make sure that the ‘server.ssl.certificate’ stanza points to the full path of the certificate and ‘server.ssl.key’ stanza points to the full path of the private keys.
  • After editing and saving kibana.yml, come to the command prompt. Enter cd /opt/KHIKA and fire command “./khika_appserver.sh stop”
  • Wait for some time (2 to 3 minutes)
  • Fire command ‘./khika_appserver.sh start’ from /opt/KHIKA directory
  • Connect using the fresh session of the browser
  • Login using default credentials (i.e. username = admin, password = admin).