14.4.1 Using a Self-Signed Server Keystore
This section describes the steps to generate a self-signed keystore into
/etc/oracle/graph
and configure the graph server (PGX) and
client to use the keystore.
- Generating a Self-Signed Server Keystore
You can create a server key store using thekeytool
command. - Configuring the Graph Server (PGX) When Using a Server Keystore
You must specify the path to the server keystore in the graph server (PGX) configuration file. - Configuring a Client to Trust the Self-Signed Keystore
You must configure your client application to accept the self-signed keystore.
Parent topic: Setting Up Transport Layer Security
14.4.1.1 Generating a Self-Signed Server Keystore
You can create a server key store using the keytool
command.
Parent topic: Using a Self-Signed Server Keystore
14.4.1.2 Configuring the Graph Server (PGX) When Using a Server Keystore
You must specify the path to the server keystore in the graph server (PGX) configuration file.
Note:
If you deploy the graph server into your web server using the web applications download package, then this section does not apply. Please refer to the manual of your web server for instructions on how to configure TLS.Parent topic: Using a Self-Signed Server Keystore
14.4.1.3 Configuring a Client to Trust the Self-Signed Keystore
You must configure your client application to accept the self-signed keystore.
- For a Java or a Python client, you must import the root certificate to all the Java installations used by all the clients.
- For the Graph Visualization application, you must import the root certificate to the system Java installation of the environment running the graph server (PGX) or the web server serving the graph visualization application. That is, the JDK installation which is used by the OS user running the server that serves the Graph Visualization application.
You can import the root certificate as shown in the following step:
Parent topic: Using a Self-Signed Server Keystore