![]() ![]() Please refer to the ClientPolicy page on the Aerospike Java client API for more details about each policy settings. The REST Client allows modification of the internal Aerospike client policies using the following environment variables. Available values can be aquired using SSLSocket.getSupportedProtocols(). An optional comma separated list of protocols that are permitted to be used in communication with Aerospike.Available cipher names can be obtained by SSLSocket.getSupportedCipherSuites(). An optional comma separated list of ciphers that are permitted to be used in communication with Aerospike.Boolean indicating that SSL should only be used for the initial login connection to Aerospike.May be omitted if the TrustStore is not password protected. If omitted the default Java TrustStore location and password will be used. The path to a Java TrustStore to be used to interact with the Aerospike Server.If omitted, and is provided, the value of will be used as the key password. The password for the key to be used when communicating with Aerospike.If a keystore path is specified, this must be specified as well. If omitted the default Java KeyStore location and password will be used. The path to a Java KeyStore to be used to interact with the Aerospike Server.If no other SSL environment variables are provided, the REST client will attempt to establish a secure connection utilizing the default Java SSL trust and keystore settings. boolean, set to true to enable a TLS connection with the Aerospike Server.For example: localhost:cluster-tls-name:4333 The following environment variables allow configuration of this connection: If utilizing TLS, the variable should be set to include appropriate TLS Names for each of the Aerospike Nodes. (This feature requires an Enterprise Edition Aerospike Server). Please note that an oversized client cache will consume a lot of resources and affect the performance.īeginning with version 1.1.0 the Aerospike REST Client supports TLS communication between the client and the Aerospike Server. Represents the max size of the authenticated clients LRU cache (default value: 16).Set this boolean flag to true to require the Basic Authentication on each request.Set custom multi-user authentication configuration variables if needed: To utilize the multi-tenancy capability within the REST Client, send Aerospike login credentials using the Basic access authentication. Default is empty and does not validate target cluster name. Supported modes are INTERNAL, EXTERNAL and EXTERNAL_INSECURE. This variable is only needed when the Aerospike cluster is running with security enabled. ![]() This is the password for the previously specified user.This is the name of a user registered with the Aerospike database.The following environment variables are used to find authentication information. The REST Client also allows authentication to an Aerospike Enterprise edition server with security enabled. If this is specified, it overrides the previous two environment variables. A comma separated list of cluster hostnames, (optional TLS names) and ports.The port to communicate with the Aerospike cluster over.Note: If TLS is being utilized, should be used instead of this variable. The IP address or Hostname of a seed node in the cluster (default: localhost).server.port Change the port the REST Client is listening on (default: 8080).Read more about Spring Boot Externalized Configuration. The Swagger specification, in JSON format, can be found at. Test out various commands in your browser. Interactive API documentation may be found at. Curl This will return basic information about the cluster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |