infinispan 0.12.0 → 0.13.0

package/documentation/asciidoc/topics/proc_installing_clients.adoc

@@ -1,58 +0,0 @@
-[id='installing-clients_{context}']
-= Installing {hr_js} clients
-{brandname} provides a distribution of the {hr_js} client that you can install via the NPM package manager.
-
-.Prerequisites
-
-* Node.js version `12` or `14`.
-//Community content
-ifdef::community[]
-* {brandname} Server 9.4.x or later.
-+
-Use js-client `0.7` for {brandname} Server `8.2.x` to `9.3.x`.
-endif::community[]
-//Downstream content
-ifdef::downstream[]
-* {brandname} Server {ProductVersion}.
-endif::downstream[]
-
-.Procedure
-
-//Community content
-ifdef::community[]
-* Install the `infinispan` client as follows:
-+
-[source,options="nowrap",subs=attributes+]
-----
-npm install infinispan
-----
-endif::community[]
-
-//Downstream content
-ifdef::rhdg-install-npmrepo[]
-. Add the Red Hat repository to your NPM configuration.
-+
-You can use the `npm config` command or add the following to an `.npmrc` file in your project:
-+
-[source,options="nowrap",subs=attributes+]
-----
-@redhat:registry=https://npm.registry.redhat.com
-registry=https://registry.npmjs.org/
-----
-
-. Install the {hr_js} client as follows:
-+
-[source,options="nowrap",subs=attributes+]
-----
-npm install @redhat/infinispan
-----
-endif::rhdg-install-npmrepo[]
-ifdef::rhdg-install-package[]
-. Download and extract the `redhat-datagrid-<version>-nodejs-client.zip` from the {portal}.
-. Install the `tgz` package from the extracted directory as in the following example:
-+
-[source,bash,options="nowrap",subs=attributes+]
-----
-npm install /path/to/redhat-datagrid-<version>-nodejs-client/infinispan-<version>.tgz
-----
-endif::rhdg-install-package[]

package/documentation/asciidoc/topics/proc_switching_clusters.adoc

@@ -1,17 +0,0 @@
-[id='switching-clusters_{context}']
-= Manually switching {brandname} clusters
-Change the {brandname} cluster to which the {hr_js} client is connectioned.
-
-.Prerequisites
-
-* Define {brandname} clusters in the {hr_js} client configuration.
-
-.Procedure
-
-. Call the `switchToCluster(clusterName)` method to force the client to switch to a {brandname} cluster that is defined in the client configuration.
-. Call the `switchToDefaultCluster()` method to start using the initial {brandname} cluster.
-+
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/connection-xsite-cluster-switch.js[]
-----

package/documentation/asciidoc/topics/ref_authentication_mechanisms.adoc

@@ -1,68 +0,0 @@
-[id='authentication-mechanisms_{context}']
-= SASL authentication mechanisms
-
-{hr_js} clients can use the following SASL authentication mechanisms to connect to {brandname} Server.
-
-[discrete]
-== PLAIN
-
-Sends credentials in plain text (unencrypted) over the wire in a way that is similar to HTTP `BASIC` authentication.
-
-[IMPORTANT]
-====
-To secure {brandname} credentials, you should use `PLAIN` authentication only in combination with TLS encryption.
-====
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/authentication-plain.js[]
-----
-
-[discrete]
-== DIGEST-MD5
-
-Uses the MD5 hashing algorithm in addition to nonces to encrypt credentials.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/authentication-digest.js[]
-----
-
-[discrete]
-== SCRAM
-
-Uses salt values in addition to hashing algorithms and nonce values to encrypt credentials.
-Hot Rod endpoints support `SCRAM-SHA-1`, `SCRAM-SHA-256`, `SCRAM-SHA-384`, `SCRAM-SHA-512` hashing algorithms, in order of strength.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/authentication-scram.js[]
-----
-
-//Community content
-ifdef::community[]
-[discrete]
-== EXTERNAL
-
-Uses client certificates to provide valid identities to {brandname} Server and enable encryption.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/authentication-external.js[]
-----
-
-
-[discrete]
-== OAUTHBEARER
-
-Uses tokens obtained via an OAuth 2.0 provider to securely connect to {brandname} Server.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/authentication-oauthbearer.js[]
-----
-endif::community[]
-
-[role="_additional-resources"]
-.Additional resources
-* link:{server_docs}#endpoint-authentication[Configuring Endpoint Authentication Mechanisms]

package/documentation/asciidoc/topics/ref_client_usage.adoc

@@ -1,128 +0,0 @@
-[id='client-usage_{context}']
-= {hr_js} client examples
-
-After you install and configure your {hr_js} client, start using it by trying out some basic cache operations before moving on to more complex interactions with {brandname}.
-
-== Hello world
-
-Create a cache named "myCache" on {brandname} Server then add and retrieve an entry.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/hello-world.js[]
-----
-
-== Working with entries and retrieving cache statistics
-
-Add, retrieve, remove single entries and view statistics for the cache.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/single-entries.js[]
-----
-
-== Working with multiple cache entries
-
-Create multiple cache entries with simple recursive loops.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/multiple-entries.js[]
-----
-
-== Using Async and Await constructs
-
-Node.js provides `async` and `await` constructs that can simplify cache operations.
-
-.Single cache entries
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/await-single-entries.js[]
-----
-
-.Multiple cache entries
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/await-multiple-entries.js[]
-----
-
-== Running server-side scripts
-
-You can add custom scripts to {brandname} Server and then run them from {hr_js} clients.
-
-.Sample script
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/sample-script.js[]
-----
-
-.Script execution
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/sample-script-execute.js[]
-----
-
-== Registering event listeners
-
-Event listeners notify {hr_js} clients when cache updates occur, including when entries are created, modified, removed, or expired.
-
-[NOTE]
-====
-Events for entry creation and modification notify clients about keys and values.
-Events for entry removal and expiration notify clients about keys only.
-====
-
-.Event listener registration
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/register-event-listener.js[]
-----
-
-You can tune notifications from event listeners to avoid unnecessary roundtrips with the `key-value-with-previous-converter-factory` converter.
-This allows you to, for example, find out values associated with keys within the event instead of retrieving them afterwards.
-
-.Remote event converter
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/key-value-converter.js[]
-----
-
-[TIP]
-====
-You can add custom converters to {brandname} Server.
-See the link:{doc_home}[{brandname} documentation] for information.
-====
-
-== Using conditional operations
-
-The Hot Rod protocol stores metadata about values in {brandname}.
-This metadata provides a deterministic factor that lets you perform cache operations for certain conditions.
-For example, if you want to replace the value of a key if the versions do not match.
-
-Use the `getWithMetadata` method to retrieve metadata associated with the value for a key.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/conditional-operations.js[]
-----
-
-== Working with ephemeral data
-
-Use the `getWithMetadata` and `size` methods expire cache entries.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/ephemeral-data.js[]
-----
-
-== Working with queries
-
-Use the `query` method to perform queries on your caches.
-You must configure {hr_js} client to have `application/x-protostream` data format for values in your caches.
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/queries.js[]
-----
-
-See link:{query_docs}[Querying {brandname} caches] for more information.

package/documentation/asciidoc/topics/ref_encryption.adoc

@@ -1,71 +0,0 @@
-[id='encryption_{context}']
-= Encryption types
-
-{hr_js} clients can use different types of encryption to negotiate secure connections with {brandname} Server.
-
-[discrete]
-== {brandname} Server identities
-
-For basic encryption, you can add the signing certificate, or CA bundle, for {brandname} Server certificates to your configuration as follows:
-
-[NOTE]
-====
-To verify certificates issued to {brandname} Server, {hr_js} clients require either the full certificate chain or a partial chain that starts with the Root CA.
-====
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/encryption-trust-certs.js[]
-----
-
-[discrete]
-== Trust stores
-
-You can add trust stores in `PKCS12` or `PFX` format as follows:
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/encryption-crypto-store.js[]
-----
-
-[discrete]
-== Client certificate authentication
-
-If you enable client certificate authentication in {brandname} Server configuration, add a keystore as in the following example:
-
-[NOTE]
-====
-You must configure the {hr_js} client with the `EXTERNAL` authentication mechanism when using client certificate authentication.
-====
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/encryption-private-key.js[]
-----
-
-[discrete]
-== Server Name Indication (SNI)
-
-If you use SNI to allow {hr_js} clients to request {brandname} Server hostnames, set a value for the `sniHostName` parameter that matches a hostname in the {brandname} Server configuration.
-
-[NOTE]
-====
-The `sniHostName` parameter defaults to `localhost`.
-====
-
-[source,javascript,options="nowrap",subs=attributes+]
-----
-include::code_examples/encryption-sni-hostname.js[]
-----
-
-[TIP]
-====
-{hr_js} clients do not allow self-signed certificates by default, which can cause issues in development or test environments where no public certificate authority (CA) key is available.
-
-Check out the link:{code_tutorials}[{brandname} code tutorials] for an example on creating signed certificates with the Java keytool.
-====
-
-[role="_additional-resources"]
-.Additional resources
-* link:{server_docs}#interfaces-endpoints[Network interfaces and endpoints]
-* link:{server_docs}#endpoint-encryption[Encrypting {brandname} Server connections]

package/gen-jsdoc.sh

@@ -1,6 +0,0 @@
-#!/usr/bin/env bash
-
-# Stop if any errors found
-set -e
-
-./node_modules/.bin/jsdoc lib/*.js

package/make-ssl.sh

@@ -1,335 +0,0 @@
-#!/bin/bash
-
-set -e -x
-
-ROOT="out"
-PASS="secret"
-
-#CA_ALIAS="infinispan-ca"
-#CA_DIR=${ROOT}/ssl/ca
-#CA_KEYSTORE="ca.jks"
-
-# Remove any previous certificate
-rm -drf ${ROOT}/ssl
-
-
-# Create keystore
-create_keystore() {
-   local alias=$1
-   local dname=$2
-   local dir=$3
-   local keystore=$4
-
-   keytool -genkeypair \
-      -alias $alias \
-      -dname $dname \
-      -keystore $dir/$keystore \
-      -storepass $PASS \
-      -keypass $PASS \
-      -keyalg RSA \
-      -keysize 2048 \
-      -storetype JKS
-}
-
-
-# Create certificate sign request
-create_sign_request() {
-   local alias=$1
-   local dname=$2
-   local dir=$3
-   local keystore=$4
-   local csr=$5
-
-   keytool -certreq \
-      -alias $alias \
-      -dname $dname \
-      -keystore $dir/$keystore \
-      -storepass $PASS \
-      -keypass $PASS \
-      -file $dir/$csr
-}
-
-
-# Sign certificate with CA
-sign_certificate() {
-   local ca=$1
-   local dir=$2
-   local csr=$3
-   local cer=$4
-
-   local ca_alias="infinispan-$ca"
-   local ca_dir=${ROOT}/ssl/$ca
-   local ca_keystore="$ca.jks"
-
-   keytool -gencert \
-      -alias $ca_alias \
-      -keystore $ca_dir/$ca_keystore \
-      -storepass $PASS \
-      -keypass $PASS \
-      -infile $dir/$csr \
-      -outfile $dir/$cer
-}
-
-
-# Import CA keystore into keystore
-import_ca() {
-   local ca=$1
-   local dir=$2
-   local keystore=$3
-
-   local ca_alias="infinispan-$ca"
-   local ca_dir=${ROOT}/ssl/$ca
-   local ca_keystore="$ca.jks"
-
-   keytool -importkeystore \
-      -srcalias $ca_alias \
-      -srcstorepass $PASS \
-      -srckeystore $ca_dir/$ca_keystore \
-      -deststorepass $PASS \
-      -destkeystore $dir/$keystore
-}
-
-
-# Import certificate into keystore
-import_certificate() {
-   local alias=$1
-   local dir=$2
-   local keystore=$3
-   local cer=$4
-
-   keytool -importcert \
-      -alias $alias \
-      -keystore $dir/$keystore \
-      -storepass $PASS \
-      -keypass $PASS \
-      -file $dir/$cer
-}
-
-
-# Convert into a p12 keystore
-keystore_to_p12() {
-   local dir=$1
-   local keystore=$2
-   local p12store=$3
-
-   keytool -importkeystore \
-      -srckeystore $dir/$keystore \
-      -destkeystore $dir/$p12store \
-      -srcstoretype jks \
-      -deststoretype pkcs12 \
-      -srcstorepass $PASS \
-      -deststorepass $PASS
-}
-
-
-# Extract client certificate as pem
-extract_pem_certificate() {
-   local dir=$1
-   local p12store=$2
-   local pem=$3
-
-   openssl pkcs12 \
-      -in $dir/$p12store \
-      -passin pass:$PASS \
-      -passout pass:$PASS \
-      -nokeys \
-      -clcerts \
-      | awk '/-BEGIN CERTIFICATE-/{a=1};a;/-END CERTIFICATE-/{exit}' \
-      > $dir/$pem
-}
-
-
-make_ca() {
-   local name=$1
-   local dir=${ROOT}/ssl/$name
-   local alias="infinispan-$name"
-   local dname="CN=CA,OU=Infinispan,O=JBoss,L=RedHat"
-   local keystore="$name.jks"
-   local p12store="$name.p12"
-   local pem="$name.pem"
-   local pass="secret"
-
-   # Make directories to work from
-   mkdir -p $dir
-
-   # Create your very own Root Certificate Authority
-   keytool -genkeypair \
-      -alias $alias \
-      -dname $dname \
-      -keystore $dir/$keystore \
-      -storepass $pass \
-      -keypass $PASS \
-      -keyalg RSA \
-      -keysize 2048 \
-      -storetype JKS \
-      -ext bc:c
-
-   # Convert into a p12 keystore
-   keytool -importkeystore \
-      -srckeystore $dir/$keystore \
-      -destkeystore $dir/$p12store \
-      -srcstoretype jks \
-      -deststoretype pkcs12 \
-      -srcstorepass $pass \
-      -deststorepass $pass
-
-   # Extract pem
-   openssl pkcs12 \
-      -in $dir/$p12store \
-      -out $dir/$pem \
-      -passin pass:$pass \
-      -passout pass:$pass \
-      -nokeys
-}
-
-
-make_server_keystore() {
-   local ca=$1
-   local dir=${ROOT}/ssl/server
-   local alias="server"
-
-   # CN has to match Hostname/IP, otherwise you get:
-   # Hostname/IP doesn't match certificate's altnames: "Host: localhost. is not cert's CN: Server"
-   local dname="CN=localhost,OU=Infinispan,O=JBoss,L=RedHat"
-
-   local keystore="server.jks"
-   local p12store="server.p12"
-   local csr="server.csr"
-   local pass="secret"
-   local cer="server.cer"
-
-   local ca_dir=${ROOT}/ssl/$ca # TODO global
-   local ca_keystore="$ca.jks" # TODO global
-   local ca_alias="infinispan-$ca" # TODO global
-
-   # Make directories to work from
-   mkdir -p $dir
-
-   # Create server keystore
-   create_keystore $alias $dname $dir $keystore
-
-   # Create certificate sign request
-   keytool -certreq \
-      -alias $alias \
-      -dname $dname \
-      -keystore $dir/$keystore \
-      -storepass $pass \
-      -keypass $PASS \
-      -file $dir/$csr \
-
-   # Sign certicate with CA
-   keytool -gencert \
-      -alias $ca_alias \
-      -keystore $ca_dir/$ca_keystore \
-      -storepass $pass \
-      -keypass $PASS \
-      -infile $dir/$csr \
-      -outfile $dir/$cer
-
-   # Import CA keystore into server keystore
-   keytool -importkeystore \
-      -srcalias $ca_alias \
-      -srcstorepass $pass \
-      -srckeystore $ca_dir/$ca_keystore \
-      -deststorepass $pass \
-      -destkeystore $dir/$keystore
-
-   # Import server certificate into server keystore
-   keytool -importcert \
-      -alias $alias \
-      -keystore $dir/$keystore \
-      -storepass $pass \
-      -keypass $PASS \
-      -file $dir/$cer
-
-   # Convert into a p12 keystore
-   keytool -importkeystore \
-      -srckeystore $dir/$keystore \
-      -destkeystore $dir/$p12store \
-      -srcstoretype jks \
-      -deststoretype pkcs12 \
-      -srcstorepass $pass \
-      -deststorepass $pass
-}
-
-
-make_client_keystore() {
-   local ca=$1
-   local dir=${ROOT}/ssl/client
-   local alias="client"
-
-   # CN has to match Hostname/IP, otherwise you get:
-   # Hostname/IP doesn't match certificate's altnames: "Host: localhost. is not cert's CN: Server"
-   local dname="CN=localhost,OU=Infinispan,O=JBoss,L=RedHat"
-
-   local keystore="client.jks"
-   local p12store="client.p12"
-   local pass="secret"
-   local csr="client.csr"
-   local cer="client.cer"
-   local pem="client.pem"
-   local privkey="client.pk"
-
-   # Make directories to work from
-   mkdir -p $dir
-
-   create_keystore $alias $dname $dir $keystore
-   create_sign_request $alias $dname $dir $keystore $csr
-   sign_certificate $ca $dir $csr $cer
-   import_ca $ca $dir $keystore
-   import_certificate $alias $dir $keystore $cer
-   keystore_to_p12 $dir $keystore $p12store
-   extract_pem_certificate $dir $p12store $pem
-
-   # Extract client private key as pem
-   openssl pkcs12 \
-      -in $dir/$p12store \
-      -passin pass:$pass \
-      -passout pass:$pass \
-      -nocerts \
-      -nodes \
-      | awk '/-BEGIN PRIVATE KEY-/{a=1};a;/-END PRIVATE KEY-/{exit}' \
-      > $dir/$privkey
-}
-
-
-make_sni() {
-   local ca=$1
-   local host=$2
-   local dir=${ROOT}/ssl/sni-$host
-   local alias=$host
-
-   # CN has to match Hostname/IP
-   local dname="CN=$host,OU=Infinispan,O=JBoss,L=RedHat"
-
-   local keystore="$host.jks"
-   local p12store="$host.p12"
-   local csr="$host.csr"
-   local cer="$host.cer"
-   local pem="$host.pem"
-
-   # Make directories to work from
-   mkdir -p $dir
-
-   create_keystore $alias $dname $dir $keystore
-   create_sign_request $alias $dname $dir $keystore $csr
-   sign_certificate $ca $dir $csr $cer
-   import_ca $ca $dir $keystore
-   import_certificate $alias $dir $keystore $cer
-   keystore_to_p12 $dir $keystore $p12store
-   extract_pem_certificate $dir $p12store $pem
-}
-
-
-main() {
-   make_ca ca
-   make_server_keystore ca
-   make_client_keystore ca
-   make_sni ca trust1
-   make_sni ca trust2
-   make_ca untrust-ca
-   make_sni untrust-ca untrust
-}
-
-
-main

package/memory-profiling/helper.js

@@ -1,9 +0,0 @@
-const fs = require('fs');
-const v8 = require('v8');
-
-exports.createHeapSnapshot = function() {
-  const snapshotStream = v8.getHeapSnapshot();
-  const fileName = `${Date.now()}.heapsnapshot`;
-  const fileStream = fs.createWriteStream('/tmp/' + fileName);
-  snapshotStream.pipe(fileStream);
-}