Protocols: Asadmin Commands
The following asadmin commands are available for administering HTTP protocols instead of using the admin console. The parameters are all explained in the configuration options above.
set-network-protocol-security-configuration
Since Payara Server 5.21.0
This command sets various options for the security of a HTTP protocol. Many options for configuring security can be done with this single asadmin command.
Usage
asadmin> set-network-protocol-security-configuration --enabled true --tls11-enabled false --tls13enabled true http-listener-2
Command Options
Option | Type | Description | Default | Mandatory |
---|---|---|---|---|
|
String |
The name of the instance to get the certificate from. |
server |
no |
|
Boolean |
If security should be enabled for the listener. |
no |
|
|
Boolean |
If HTTP listeners on the server should be restarted. |
no |
|
|
Boolean |
If TLS version 1.0 should be enabled. |
no |
|
|
Boolean |
If TLS version 1.1 should be enabled. |
no |
|
|
Boolean |
If TLS version 1.2 should be enabled. |
no |
|
|
Boolean |
If TLS version 1.3 should be enabled. |
no |
|
|
String |
Name of the keystore file i.e. keystore.jks |
no |
|
|
String |
Password for the keystore file. |
no |
|
|
String |
Name of the truststore file i.e cacerts.jks. |
no |
|
|
String |
Password for the truststore file. |
no |
|
|
Boolean |
Name of the trust management algorithm (for example, PKIX) to use for certification path validation. |
no |
|
|
Integer |
How long before TLS session expire from the cache. |
no |
|
|
Integer |
How large the TLS session cache can get. |
no |
|
|
String |
Takes a single value, identifies the server’s default keypair and certificate. |
no |
|
|
want,need, |
Determines if if the engine will request (want) or require (need) client authentication. |
no |