Tip |
---|
When you run the keytool -importpass command, it always prompts for a "password". This is because the keytool does not distinguish between the secrets that it stores. At the prompt, enter the actual value you want to store securely. |
If you are creating the keystore on Windows, you must use the backslash \
in the path. PhixFlow will not be able to read the pepper key value if you use the forward slash /
.
Note |
---|
If you have follow the recommended instructions for installing Java (Install Java) the keytool program will be in your path. If you have take a different approach, you can find the keytool program under JAVA_INSTALLATION_HOME/bin . |
- Run the
-importpass
command, specifying the alias: pepperKey
The alias is case-sensitive and must match phixflow-instance.xml: <prop key="pepperKey">pepperKey</prop>
If you use a different alias, update phixflow-instance.xml to use the same alias. When prompted, enter the password you want to set for the keystore file, then re-enter to confirm it.
Keep a secure record of this password.
Tip |
---|
If you are following these instructions to upgrade PhixFlow, and your keystore already exists, in step 2 enter the password for your keystore. See also: Adding Data to a Keystore |
- When prompted for the password, enter the string you want to use to pepper user passwords.
We recommend this string has the same characteristics as a password. For example it should be a random string containing at least 6 letters, numbers and special characters.
Keep a secure record of the pepper key.
Code Block |
---|
title | Windows Command Line Example |
---|
|
keytool -importpass -alias pepperKey -keystore C:\secure\keystore.jks -storetype PKCS12 |
Code Block |
---|
title | Windows Powershell Example |
---|
|
keytool -importpass -alias pepperKey -keystore C:\secure\keystore.jks -storetype PKCS12 |
Code Block |
---|
|
keytool -importpass -alias pepperkey -keystore /opt/secure/keystore.jks -storetype PKCS12 |
1.1 Run the -importpass
command, specifying the alias username for the PhixFlow database, for example phixflow-database-user
.
1.2 When prompted, enter the keystore password.
1.3 When prompted for the password, enter the actual username for the PhixFlow database, for example phixflow
.
Code Block |
---|
title | Windows Command Line |
---|
|
keytool -importpass -alias phixflow-database-user -keystore C:\secure\keystore.jks -storetype PKCS12 |
Code Block |
---|
title | Windows Powershell Example |
---|
|
keytool -importpass -alias phixflow-database-user -keystore C:\secure\keystore.jks -storetype PKCS12 |
Code Block |
---|
|
keytool -importpass -alias phixflow-database-user -keystore /opt/secure/keystore.jks -storetype PKCS12 |
2.1. Run the -importpass
command specifying the alias password for the PhixFlow database, for example phixflow-database-password
.
2.2 When prompted, enter the keystore password.
2.3 When prompted for the password, enter the actual password for the PhixFlow database.
Code Block |
---|
title | Windows Command Line Example |
---|
|
keytool -importpass -alias phixflow-database-password -keystore C:\secure\keystore.jks -storetype PKCS12 |
Code Block |
---|
title | Windows Powershell Example |
---|
|
keytool.exe -importpass -alias phixflow-database-password -keystore C:\secure\keystore.jks -storetype PKCS12 |
Code Block |
---|
|
keytool -importpass -alias phixflow-database-password -keystore /opt/secure/keystore.jks -storetype PKCS12 |
Edit phixflow-datasource.xml to add the aliases for the PhixFlow database username and password. For example:
Code Block |
---|
<property name="username">
<value>phixflow-database-user</value>
</property>
<property name="password">
<value>phixflow-database-password</value>
</property> |
Note |
---|
We recommend that you use an environment variable for the keystore password, as it provides additional security. If you do not set an environment variable, you must include the keystore password in phixflow-secret.xml. |
Create an environment variable with the form <variable-name>: <keystore-password>
| In Windows | In Linux |
---|
<variable-name> | In Windows: In the environment variable, specify any variable name you choose. | Use the EnvironmentFile directive in the systemd service definition. Ensure that only root can read/write EnvironmentFile . For information about how to set environment variables in Linux, see: |
<keystore-password> | Specify the password for the keystore. |
Warning |
---|
Never add the keystore password to the profile for the Tomcat user. |
Copy phixflow-secret.xml.example to phixflow-secret.xml and edit it to set the values as follows:
Required? | Property | Value | Example |
---|
Required | keystoreType | The type of the keystore, either PKCS12 or JCEKS | <!-- keystore type (PKCS12 or JCEKS) -->
<property name="keystoreType"> <value>PKCS12</value> </property>
|
Required | keystoreFile | The path to the keystore. | <!-- keystore filepath -->
<property name="keystoreFile"> <value>/opt/secure/keystore.jks </value> </property>
|
Either (recommended) | keystorePassEnvironmentVariable | The name of the environment variable. Use <!-- and --> to comment out the keystorePass property.
Info |
---|
When specifying the value for the password in an environment variable, the value entered should adhere the policy of the environment variables for your operating system. |
| <!-- keystore password -->
<property name="keystorePassEnvironmentVariable"><value>KEY_PASS</value>
</property>
|
Or | keystorePass | The password for the keystore. Use <!-- and --> to comment out the keystorePassEnvironmentVariable property. Info |
---|
When specifying the value for the password in the phixflow-secret.xml, special characters will need to be escaped. |
| <!-- keystore password -->
<property name="keystorePass"> <value>storepw</value> </property>
|
Warning |
---|
On startup, PhixFlow checks that there is one password mechanism, either keystorePassEnvironmentVariable or keystorePass . Do not specify both as this will prevent PhixFlow from running. |
To The process for logic is to create a new keystore is:
- Tomcat will need to be stopped.
- Import the existing keystore, source"src", at which point you will be prompted for its password, into a new destination keystore instance that has a new password.
- The keytool will prompt you for the password for the old keystore and then it will prompt you for a new password for the new keystore.
- You will then need to point the PhixFlow phixFlow-Secretsecret.xml at the new keystore, and update keystore password in this file or the environment variable.
Code Block |
---|
title | Linux |
---|
linenumbers | true |
---|
|
keytool -importkeystore \
-srckeystore keystore.jks -srcstoretype PKCS12 \
-destkeystore keystore2.jks -deststoretype PKCS12 |
Code Block |
---|
title | Windows |
---|
linenumbers | true |
---|
|
keytool -importkeystore \
-srckeystore keystore.jks -srcstoretype PKCS12 \
-destkeystore keystore2.jks -deststoretype PKCS12 |