Releases: couchbase/couchbase-elasticsearch-connector
v2.2.3.2-update2 with support for JDK 1.7
This version uses an updated CAPI server v1.4.1, which downgrades Jetty to 9.2.17.v20160517, the last version to support JDK 1.7
2.5.0.0-alpha2 release with support for ES 5.0.0-alpha2
This is a preview release of the plugin for Elasticsearch 5.0.0-alpha2 (https://www.elastic.co/blog/elasticsearch-5-0-0-alpha2-released) with improved setting validation and better security management.
To install the plugin, run:
bin/elasticsearch-plugin install -b https://github.com/couchbaselabs/elasticsearch-transport-couchbase/releases/download/2.5.0.0-alpha2/elasticsearch-transport-couchbase-2.5.0.0-alpha2.zip
v2.2.3.2-update1 with support for ES 2.3.2
This release uses CAPI server 1.4.0 with Jetty 9.3.8.v20160314, adds support for Elasticsearch 2.3.2 and removes the need for the Java security policy workaround that was required in v2.2.1. When installing the plugin, you will be asked to approve the additional security permissions, please do so. Alternatively, you can install it with the -b flag, which automatically accepts all prompts.
v2.2.3.1 with support for ES 2.3.1
This release adds support for Elasticsearch 2.3.1 and removes the need for the Java security policy workaround that was required in v2.2.1. When installing the plugin, you will be asked to approve the additional security permissions, please do so. Alternatively, you can install it with the -b flag, which automatically accepts all prompts.
v2.2.3.0 with support for ES 2.3.0
This release adds support for Elasticsearch 2.3.0 and removes the need for the Java security policy workaround that was required in v2.2.1. When installing the plugin, you will be asked to approve the additional security permissions, please do so. Alternatively, you can install it with the -b flag, which automatically accepts all prompts.
v2.2.2.2 with support for ES 2.2.2
This release adds support for Elasticsearch 2.2.2 and removes the need for the Java security policy workaround that was required in v2.2.1. When installing the plugin, you will be asked to approve the additional security permissions, please do so. Alternatively, you can install it with the -b flag, which automatically accepts all prompts.
v2.2.2.1 with support for ES 2.2.1
This release adds support for Elasticsearch 2.2.1 and removes the need for the Java security policy workaround that was required in v2.2.1. When installing the plugin, you will be asked to approve the additional security permissions, please do so. Alternatively, you can install it with the -b flag, which automatically accepts all prompts.
v2.2.2.0 with support for ES 2.2.0
This release adds support for Elasticsearch 2.2.0 and removes the need for the Java security policy workaround that was required in v2.2.1. When installing the plugin, you will be asked to approve the additional security permissions, please do so. Alternatively, you can install it with the -b flag, which automatically accepts all prompts.
v2.2.1.2 with Support for Elasticsearch 2.1.1
This release adds support for Elasticsearch 2.1.1, which was generously contributed by Perrin Bignoli (https://github.com/bignolip) to the plugin. Note that due to changes in the security mechanism of Elasticsearch the plugin now requires changes to the Java policy file as follows:
Java Security Policy Permissions
In order to get the plugin to work with ES 2.1.x, it is necessary to edit the system's default java.policy file, which is located in the %JAVA_HOME%/jre/lib/security directory. You can either edit this file directly, or use the policytool utility, which can be found in the %JAVA_HOME/bin directory. Note that editing the policy file requires root permissions.
If you're editing the policy file directly, add the following to the end of the file:
grant codeBase "file://<path to transport-couchbase plugin install directory>/*" {
permission javax.security.auth.AuthPermission "modifyPrincipals";
permission javax.security.auth.AuthPermission "modifyPrivateCredentials";
permission javax.security.auth.AuthPermission "setReadOnly";
permission java.lang.RuntimePermission "setContextClassLoader";
permission java.net.SocketPermission "*", "listen,resolve";
permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
};
Replace file://<path>/* with the directory where you installed the plugin. For example, if you installed Elasticsearch from as a deb/rpm package on Linux, this would be file:///usr/share/elasticsearch/plugins/transport-couchbase/* - note the trailing *, which means that the policy will apply to all files in that directory.
If you prefer to use the GUI applet, run specify the location of the policy file with the -file parameter, for example:
sudo $JAVA_HOME/bin/policytool -file $JAVA_HOME/jre/lib/security/java.policy
When the applet window appears, verify that the Policy File textbox shows the name of the policy file you're going to edit. To add the required security settings click on the "Add Policy Entry" button. In the new "Policy Entry" window that will appear, fill in the CodeBase textbox with the URL path to the plugin's installation directory, as explained above.
Next, add each of the following permissions by clicking on the "Add Permission" button for each, then selecting the specified options:
1.) permission javax.security.auth.AuthPermission "modifyPrincipals";
From the "Permission:" dropdown select:
AuthPermission
From the "Target Name:" dropdown select:
modifyPrincipals
Click "Ok"
2.) permission javax.security.auth.AuthPermission "modifyPrivateCredentials";
From the "Permission:" dropdown select:
AuthPermission
From the "Target Name:" dropdown select:
modifyPrivateCredentials
Click "Ok"
3.) permission javax.security.auth.AuthPermission "setReadOnly";
From the "Permission:" dropdown select:
AuthPermission
From the "Target Name:" dropdown select:
setReadOnly
Click "Ok"
4.) permission java.lang.RuntimePermission "setContextClassLoader";
From the "Permission:" dropdown select:
RuntimePermission
From the "Target Name:" dropdown select:
setContextClassLoader
Click "Ok"
5.) permission java.net.SocketPermission "*", "listen,resolve";
From the "Permission:" dropdown select:
SocketPermission
In the "Target Name:" textbox type:
*
In the "Actions:" dropdown type:
listen,resolve
Click "Ok"
6.) permission "java.lang.reflect.ReflectPermission" "suppressAccessChecks";
From the "Permission:" dropdown select:
ReflectPermission
From the "Target Name:" dropdown select:
suppressAccessChecks
Click "Ok"
At the end of the process, your policy tool should look similar to this:
v2.2.0.2 with Support for Elasticsearch 2.1.0
This release adds support for Elasticsearch 2.1.0, which was generously contributed by Perrin Bignoli (https://github.com/bignolip) to the plugin. Note that due to changes in the security mechanism of Elasticsearch the plugin now requires changes to the Java policy file as follows:
Java Security Policy Permissions
In order to get the plugin to work with ES 2.1.x, it is necessary to edit the system's default java.policy file, which is located in the %JAVA_HOME%/jre/lib/security directory. You can either edit this file directly, or use the policytool utility, which can be found in the %JAVA_HOME/bin directory. Note that editing the policy file requires root permissions.
If you're editing the policy file directly, add the following to the end of the file:
grant codeBase "file://<path to transport-couchbase plugin install directory>/*" {
permission javax.security.auth.AuthPermission "modifyPrincipals";
permission javax.security.auth.AuthPermission "modifyPrivateCredentials";
permission javax.security.auth.AuthPermission "setReadOnly";
permission java.lang.RuntimePermission "setContextClassLoader";
permission java.net.SocketPermission "*", "listen,resolve";
permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
};
Replace file://<path>/* with the directory where you installed the plugin. For example, if you installed Elasticsearch from as a deb/rpm package on Linux, this would be file:///usr/share/elasticsearch/plugins/transport-couchbase/* - note the trailing *, which means that the policy will apply to all files in that directory.
If you prefer to use the GUI applet, run specify the location of the policy file with the -file parameter, for example:
sudo $JAVA_HOME/bin/policytool -file $JAVA_HOME/jre/lib/security/java.policy
When the applet window appears, verify that the Policy File textbox shows the name of the policy file you're going to edit. To add the required security settings click on the "Add Policy Entry" button. In the new "Policy Entry" window that will appear, fill in the CodeBase textbox with the URL path to the plugin's installation directory, as explained above.
Next, add each of the following permissions by clicking on the "Add Permission" button for each, then selecting the specified options:
1.) permission javax.security.auth.AuthPermission "modifyPrincipals";
From the "Permission:" dropdown select:
AuthPermission
From the "Target Name:" dropdown select:
modifyPrincipals
Click "Ok"
2.) permission javax.security.auth.AuthPermission "modifyPrivateCredentials";
From the "Permission:" dropdown select:
AuthPermission
From the "Target Name:" dropdown select:
modifyPrivateCredentials
Click "Ok"
3.) permission javax.security.auth.AuthPermission "setReadOnly";
From the "Permission:" dropdown select:
AuthPermission
From the "Target Name:" dropdown select:
setReadOnly
Click "Ok"
4.) permission java.lang.RuntimePermission "setContextClassLoader";
From the "Permission:" dropdown select:
RuntimePermission
From the "Target Name:" dropdown select:
setContextClassLoader
Click "Ok"
5.) permission java.net.SocketPermission "*", "listen,resolve";
From the "Permission:" dropdown select:
SocketPermission
In the "Target Name:" textbox type:
*
In the "Actions:" dropdown type:
listen,resolve
Click "Ok"
6.) permission "java.lang.reflect.ReflectPermission" "suppressAccessChecks";
From the "Permission:" dropdown select:
ReflectPermission
From the "Target Name:" dropdown select:
suppressAccessChecks
Click "Ok"
At the end of the process, your policy tool should look similar to this: