Overview

PhixFlow uses a Java keystore for data that needs to be secure. When PhixFlow is installed, the keystore is created and the following are added:

• a pepper string used to encrypt local user password
• username and password for the PhixFlow database

The instructions for this are in the Installing PhixFlow topic: see Configure a Keystore and Aliases.

We recommend that you also store other credentials in the keystore, such as those provided:

• to a database by an analysis model datasource instance
• by system notification email accounts.

You can then use an alias to retrieve the data from the keystore.

You will need to provide PhixFlow users with the alias that they need to configure secure:

• datasources
• email accounts.

Keytool

Syntax 

Anchor
syntax syntax

The keytool command

syntax  to add entries is:

<keytool> -importpass -alias <key> -keystore <file> -storetype <type>

The keytool command syntax to delete entries is:

<keytool> -delete -alias <key> -keystore <file>

To add data to the keystore, use the Java keytool -importpass line command. From a command prompt:

1. Enter the -importpass command, specifying an alias

1. (key).
2. When the keytool prompts, enter the keystore's password.
3. When the keytool prompts again for a "password", enter the string you want to store, usually a user name or password. 

To add a username and password to the keystore,

you need to run the command twice. For example:

• a keystore is called secure.jks
• its password is keypass
• The datasource instance details you want to store are:
  • username sqluser, wth the key db1
  • password x34!2axf with the key db1pass

Windows example:

keytool -importpass -alias db1pass -keystore /opt/secure/secure.jks -storetype PKCS12
keypass
x34!2axf

Changing Keystore Entries

It is not possible to change a username or password when it is in the keystore. Instead, you have to:

• delete the entry using the keytool -delete command; see Keystore Syntax, above.
• add a different username or password using the keytool -importpass command, using the same alias.

For the commands, see Keystore Syntax, above.

Keystores for Multiple Instances

If you are running more than one PhixFlow instance, you may have a keystore for each instance. In this case, you can use the same alias in each keystore. For example, each keystore can have a "pepperKey" or "databasePassword".

If you are using one keystore for multiple PhixFlow instances, then each instance must have a unique alias. It is good practice for the alias to clearly indicate the instance. For example if you have separate Production and Development instances you could use the aliases:

• ProdDatabasePassword, DevDatabasePassword
• ProdPepperKey, DevPepperKey.
  Remember to update phixflow-instance.xml to refer to the pepper alias you set in the keystore.

Understanding How PhixFlow Uses A Keystore

PhixFlow has a secret service wrapper that it uses to communicate with the keystore. The configuration file webapp/WEB-INF/classes/phixflow-secret.xml tells Phixflow where to find the keystore file and its password. PhixFlow periodically checks the keystore based on the retryDelay. This defaults to 10 seconds, set in milliseconds. This means PhixFlow can use updated information in the keystore without requiring a Tomcat restart.

Example: Accessing the PhixFlow Database

This example illustrates how PhixFlow uses a keystore to access its own database.When PhixFlow is running, it provides the account credentials to its database as follows:

1. phixflow-datasource.xml stores alias credentials for the database. It requests actual credentials from phixflow-secret.xml.
2. phixflow-secret.xml asks the keystore for the actual credentials.
   1. The keystore password is configured as an environment variable This file stores the location of the keystore file and optionally its password (2a in the diagram below).
   2. Alternatively, phixflow-secret.xml stores the location of the keystore file and optionally its password (2b in the diagram below)
3. The keystore file returns the actual account credentials to phixflow-secret
4. which, in turn, passes the actual credentials to phixflow-datasource.xml.
5. phixflow-datasource.xml then uses the actual credentials to log into the database, so that PhixFlow can update it.

This is shown in the diagram below.