Wildfly Security Settings
If you need to secure your environment the following can be used:
HTTPS Setup
If you want to set up an HTTPS domain then the following will need to be included in the config.json. This is included in the example-configuration-secure-[version].json
.
Element | Description | Type | Required | Notes | ||
---|---|---|---|---|---|---|
"https" | dictionary | Optional | ||||
|
The location of the keystore file | string | Required if https specified | This can be an absolute path or relative to the working directory of the installer. | ||
|
The password to the keystore | string | Required if https specified | N/A | ||
|
The alias of the key you wish to use within the keystore | string | Required if https specified | N/A | ||
|
The password for the key you wish to use within the keystore | string | Required if https specified | N/A |
It is recommenced that you also set the flag below to stop cookies from being transmitted over HTTP.
Secure Cookies
If you are managing an HTTPS enabled domain, it is recommended that you set a flag which will stop cookies from being transmitted over HTTP.
Before launching the installer, open the config.json
and add the following to the jvmArgs section of each product you wish to secure:
Note: It is not recommended that you apply the flag to Snowflake products.
"jvmArgs": [
{
"name": "1sms.cookie.secure",
"value": "true"
}
]
Note: If you would like to secure products that have already been installed, this can be achieved by adding the jvmArg manually to each product you wish to secure (within the WildFly console).