- Some settings are not returned via the nodes settings API
This is intentional. Some of the settings are considered to be highly sensitive (e.g. all
hostname_verification). For this reason, we filter these settings and not exposing them via the nodes info API rest endpoint. It is also possible to define additional sensitive settings that should be hidden using the
shield.hide_settings: shield.authc.realms.ldap1.url, shield.authc.realms.ad1.*
The snippet above will also hide the
urlsettings of the
ldap1realm and all settings of the
- I configured the appropriate roles and the users, but I still get an authorization exception
Verify that the role names associated with the users match the roles defined in the
roles.ymlfile. You can use the
esuserstool to list all the users. Any unknown roles are marked with
- ERROR: extra arguments […] were provided
This error occurs when the
esuserstool is parsing the input and finds unexepected arguments. This can happen when there are special characters used in some of the arguments. For example, on Windows systems the
,character is considered a parameter separator; in other words
-r role1,role2is translated to
-r role1 role2and the
esuserstool only recognizes
role1as an expected parameter. The solution here is to quote the parameter:
- Certain users are being frequently locked out of Active Directory
Check your realm configuration; realms are checked serially, one after another. If your Active Directory realm is being checked before other realms and there are usernames that appear in both Active Directory and another realm, a valid login for one realm may be causing failed login attempts in another realm.
For example, if
UserAexists in both Active Directory and a file realm, and the Active Directory realm is checked first and file is checked second, an attempt to authenticate as
UserAin the file realm would first attempt to authenticate against Active Directory and fail, before successfully authenticating against the
filerealm. Because authentication is verified on each request, the Active Directory realm would be checked - and fail - on each request for
filerealm. In this case, while the Shield request completed successfully, the account on Active Directory would have received several failed login attempts, and that account may become temporarily locked out. Plan the order of your realms accordingly.
Also note that it is not typically necessary to define multiple Active Directory realms to handle domain controller failures. When using Microsoft DNS, the DNS entry for the domain should always point to an available domain controller.
- I can authenticate to LDAP, but I still get an authorization exception
A number of configuration options can cause this error.
Groups are located by either an LDAP search or by the "memberOf" attribute on the user. Also, If subtree search is turned off, it will search only one level deep. See the LDAP Settings for all the options. There are many options here and sticking to the defaults will not work for all scenarios.
group to role mapping
role_mapping.ymlfile or the location for this file could be misconfigured. See Shield Files for more.
roles.ymlfile or the location for this file could be misconfigured. See Shield Files for more.
To help track down these possibilities, add
shield.authc: DEBUGto the
logging.ymlconfiguration file in
CONFIG_DIR. A successful authentication should produce debug statements that list groups and role mappings.
Encryption & Certificatesedit
curlon the Mac returns a certificate verification error even when the
--cacertoption is used
Apple’s integration of
curlwith their keychain technology disables the
--cacertoption. See http://curl.haxx.se/mail/archive-2013-10/0036.html for more information.
You can use another tool, such as
wget, to test certificates. Alternately, you can add the certificate for the signing certificate authority MacOS system keychain, using a procedure similar to the one detailed at the Apple knowledge base. Be sure to add the signing CA’s certificate and not the server’s certificate.
SSLHandshakeException causing connections to failedit
SSLHandshakeException will cause a connection to a node to fail and indicates that there is a configuration issue. Some of the
common exceptions are shown below with tips on how to resolve these issues.
java.security.cert.CertificateException: No name matching node01.example.com found
Indicates that a client connection was made to
node01.example.combut the certificate returned did not contain the name
node01.example.com. In most cases, the issue can be resolved by ensuring the name is specified as a
SubjectAlternativeNameduring certificate creation. Another scenario is when the environment does not wish to use DNS names in certificates at all. In this scenario, all settings in
elasticsearch.ymlshould only use IP addresses and the following setting needs to be set in
java.security.cert.CertificateException: No subject alternative names present
Indicates that a client connection was made to an IP address but the returned certificate did not contain any
SubjectAlternativeNameentries. IP addresses are only used for hostname verification if they are specified as a
SubjectAlternativeNameduring certificate creation. If the intent was to use IP addresses for hostname verification, then the certificate will need to be regenerated. Also verify that
shield.ssl.hostname_verification.resolve_name: falseis not set in
javax.net.ssl.SSLHandshakeException: null cert chainand
javax.net.ssl.SSLException: Received fatal alert: bad_certificate
SSLHandshakeExceptionabove indicates that a self-signed certificate was returned by the client that is not trusted as it cannot be found in the
SSLExceptionabove is seen on the client side of the connection.
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested targetand
javax.net.ssl.SSLException: Received fatal alert: certificate_unknown
SunCertPathBuilderExceptionabove indicates that a certificate was returned during the handshake that is not trusted. This message is seen on the client side of the connection. The
SSLExceptionabove is seen on the server side of the connection. The CA certificate that signed the returned certificate was not found in the
truststoreand needs to be added to trust this certificate.
Other SSL/TLS related exceptionsedit
The are other exceptions related to SSL that may be seen in the logs. Below you will find some common exceptions and their meaning.
- WARN: received plaintext http traffic on a https channel, closing connection
Indicates that there was an incoming plaintext http request. This typically occurs when an external applications attempts to make an unencrypted call to the REST interface. Please ensure that all applications are using
httpswhen calling the REST interface with SSL enabled.
org.elasticsearch.common.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record:
Indicates that there was incoming plaintext traffic on an SSL connection. This typically occurs when a node is not configured to use encrypted communication and tries to connect to nodes that are using encrypted communication. Please verify that all nodes are using the same setting for
java.io.StreamCorruptedException: invalid internal transport message format, got
Indicates an issue with data received on the transport interface in an unknown format. This can happen when a node with encrypted communication enabled connects to a node that has encrypted communication disabled. Please verify that all nodes are using the same setting for
java.lang.IllegalArgumentException: empty text
The exception is typically seen when a
httpsrequest is made to a node that is not using
httpsis desired, please ensure the following setting is in
- ERROR: unsupported ciphers […] were requested but cannot be used in this JVM
This error occurs when a SSL/TLS cipher suite is specified that cannot supported by the JVM that Elasticsearch is running in. Shield will try to use the specified cipher suites that are supported by this JVM. This error can occur when using the Shield defaults as some distributions of OpenJDK do not enable the PKCS11 provider by default. In this case, we recommend consulting your JVM documentation for details on how to enable the PKCS11 provider.
Another common source of this error is requesting cipher suites that use encrypting with a key length greater than 128 bits when running on an Oracle JDK. In this case, you will need to install the JCE Unlimited Strength Jurisdiction Policy Files.