Package com.linkedin.venice
Class CommonConfigKeys
java.lang.Object
com.linkedin.venice.CommonConfigKeys
Common config keys shared by venice-backend and venice-thin-client.
-
Field Summary
Modifier and TypeFieldDescriptionstatic final String
static final String
This config defines the class name of the SSL factory.static final String
static final String
static final String
static final String
static final String
static final String
This config mainly control the SSL behavior inside AdminSparkServer.static final String
static final String
static final String
static final String
static final String
-
Constructor Summary
-
Method Summary
-
Field Details
-
SSL_ENABLED
- See Also:
-
SSL_KEYSTORE_LOCATION
- See Also:
-
SSL_KEYSTORE_PASSWORD
- See Also:
-
SSL_KEYSTORE_TYPE
- See Also:
-
SSL_KEY_PASSWORD
- See Also:
-
SSL_TRUSTSTORE_LOCATION
- See Also:
-
SSL_TRUSTSTORE_PASSWORD
- See Also:
-
SSL_TRUSTSTORE_TYPE
- See Also:
-
SSL_KEYMANAGER_ALGORITHM
- See Also:
-
SSL_TRUSTMANAGER_ALGORITHM
- See Also:
-
SSL_SECURE_RANDOM_IMPLEMENTATION
- See Also:
-
SSL_NEEDS_CLIENT_CERT
This config mainly control the SSL behavior inside AdminSparkServer. With SSL_NEEDS_CLIENT_CERT set to false, the AdminSparkServer will not check the certificate sent by client, which should be the default behavior in venice OSS project because AdminSparkServer doesn't accept the self signed certificate created in test cases. In production, we need to override this config to true to check client certificate.- See Also:
-
SSL_FACTORY_CLASS_NAME
This config defines the class name of the SSL factory. a. In the livenice, backend and VPJ product, we should override this config with the LinkedIn internal SSL factory class name. b. In open source venice project, we should use theDefaultSSLFactory
class, which is a clone implementation ofcom.linkedin.security.ssl.access.control.SSLEngineComponentFactoryImpl
(Container 25.2.15)- See Also:
-
-
Constructor Details
-
CommonConfigKeys
public CommonConfigKeys()
-