@zakaria Yes, you don’t need this.
i removed it, and still the same problem
@zakaria How many nodes do you have in the cluster?
Could you share the output of the below API request?
GET _cluster/health
Here’s the output :
> curl.exe -X GET http://localhost:9200/_cluster/health -u "admin:admin" --insecure
{"cluster_name":"opensearch","status":"yellow","timed_out":false,"number_of_nodes":1,"number_of_data_nodes":1,"discovered_master":true,"discovered_cluster_manager":true,"active_primary_shards":14,"active_shards":14,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":6,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":70.0}
@pablo when i removed the backend_roles from the internal_users.yml, now the error looks like this :
log [13:26:09.016] [error][data][opensearch] [security_exception]: no permissions for [indices:data/read/get] and User [name=client1, backend_roles=[], requestedTenant=null]
log [13:26:10.259] [error][data][opensearch] [security_exception]: no permissions for [indices:data/read/search] and User [name=client1, backend_roles=[], requestedTenant=null]
As you can see, there’s no longer the backend_role in the error, but i still have no permissions for the client1 user
@zakaria And you do have just one OpenSearch node in the cluster?
The _cluster/health represents the current working configuration. What I’d like to confirm is that you do have a single node in the cluster.
If not, and you have 2 nodes but for some reason, these are not connecting to each other then you have two clusters with single nodes using separate security configs.
You’ve mentioned that enabling security in the OpenSearch node breaks the node and you must disable SSL on 9200 to get it working.
What do you mean by that? Do you have issues connecting OpenSearch Dashboards to OpenSearch or starting the OpenSearch node?
Your OpenSearch Dashboards connects to localhost. Did you run a curl command (authinfo) against that localhost?
How did you deploy your cluster?
Yes I do have only one node in the cluster
> curl.exe -X GET http://localhost:9200/_nodes -u "admin:admin" --insecure
{"_nodes":{"total":1,"successful":1,"failed":0},"cluster_name":"opensearch", .....
And Yes i have trouble running it with https because i think the certificate isn’t recognized. In fact, it seems like the OpenSearch server is not accepting the client’s certificate (client.pem and client-key.pem in your OpenSearch Dashboard config). Here’s the error i get when i try to use HTTPS :
log [12:28:51.797] [info][listening] Server running at https://localhost:5601
log [12:28:51.954] [info][server][OpenSearchDashboards][http] http server running at https://localhost:5601
error [12:29:39.922] [error][client][connection] Error: 25192:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:...\openssl\openssl\ssl\record\rec_layer_s3.c:1563:SSL alert number 46
and here’s my configuration when enabling security :
opensearch.yml :
plugins.security.disabled: "false"
plugins.security.ssl.transport.pemcert_filepath: node1.pem
plugins.security.ssl.transport.pemkey_filepath: node1-key.pem
plugins.security.ssl.transport.pemtrustedcas_filepath: root-ca.pem
plugins.security.ssl.transport.enforce_hostname_verification: false
plugins.security.ssl.http.enabled: true
plugins.security.ssl.http.pemcert_filepath: node1.pem
plugins.security.ssl.http.pemkey_filepath: node1-key.pem
plugins.security.ssl.http.pemtrustedcas_filepath: root-ca.pem
plugins.security.authcz.admin_dn:
- 'CN=A,OU=UNIT,O=ORG,L=TORONTO,ST=ONTARIO,C=CA'
plugins.security.nodes_dn:
- 'CN=node1.dns.a-record,OU=UNIT,O=ORG,L=TORONTO,ST=ONTARIO,C=CA'
plugins.security.restapi.roles_enabled: ["all_access", "security_rest_api_access", "client1_role"]
And the opensearch_dashboards.yml file :
opensearch.hosts: ["https://localhost:9200"]
opensearch.ssl.verificationMode: none
server.ssl.enabled: true
server.ssl.certificate: "path/to/client.pem"
server.ssl.key: "path/to/client-key.pem"
opensearch.ssl.certificateAuthorities: ["path/to/root-ca.pem"]
opensearch.username: kibanaserver
opensearch.password: kibanaserver
opensearch.requestHeadersAllowlist: ["securitytenant","Authorization"]
opensearch_security.multitenancy.enabled: true
opensearch_security.multitenancy.tenants.enable_global: true
opensearch_security.multitenancy.tenants.enable_private: true
opensearch_security.multitenancy.tenants.preferred: ["Private", "Global"]
opensearch_security.multitenancy.enable_filter: false
And when i run it and access the localhost i get “Your connection is not private”.
Besides this, my main problem is the “no permissions” error when i’m working with http for testing purposes. Do you think if i was working with HTTPS i would not have this problem ?
@zakaria HTTPS is only a secured connection and doesn’t affect users’ permissions.
The reason why I was asking about the cluster, was related to the fact that you could have 2 nodes running as single-node clusters with exactly the same cluster name. As a result, you could have different security configurations in each node.
Anyway, this is not the case here.
In regards to your OpenSearch Dashboards. You can remove this line as opensearch.ssl.verificationMode: is set to none.
opensearch.ssl.certificateAuthorities: ["path/to/root-ca.pem"]
This line might be causing the reported certificate error.
“Your connection is not private” is expected when TLS self-signed certificates are used. You just accept the certificate and that will take you to OpenSearch Dashboards.
It is recommended to use HTTPS connectivity in the production environment.
In regards to the reported user. Have you tried to create a user with OpenSearch Dashboards UI?
@pablo Yes indeed, i have tried to create users, roles using the Dashboard UI, however it doesn’t change the error, i’ve also tried changing it directly in the .yml files. Do you think it is due to a multitenancy bug on opensearch 2.7 ?
@pablo It finally worked! I no longer have the permissions error, I managed to work with HTTPS instead of HTTP. I could not do it before because of a SSL error in the dashboard (number 46) but when i added the certificate into my browser it worked and i no longer had the no permissions error when logging in with the client user, also i can now visualize old logs in the dashboard. Thank you !
However, i faced another issue concerning Logstash (which i’m using as an intermediate between Filebeat and Logstash). In fact, when I try to configure it so it communicates with OpenSearch using HTTPS (otherwise i’d have an error if anything is communicating using HTTP with OpenSearch now that i’m using secured connection) , I have the following error in logstash :
[2023-05-24T11:29:34,156][WARN ][io.netty.channel.DefaultChannelPipeline][main][94a21e8610243f7243e86939f98b4336f15d3e1f1870b94ddd975b461d051b1a] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
io.netty.handler.codec.DecoderException: org.logstash.beats.InvalidFrameProtocolException: Invalid version of beats protocol: 22
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:499) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:290) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:61) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final] at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:425) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:66) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.87.Final.jar:4.1.87.Final]
at java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: org.logstash.beats.InvalidFrameProtocolException: Invalid version of beats protocol: 22
at org.logstash.beats.Protocol.version(Protocol.java:22) ~[logstash-input-beats-6.5.0.jar:?]
at org.logstash.beats.BeatsParser.decode(BeatsParser.java:62) ~[logstash-input-beats-6.5.0.jar:?]
at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:529) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:468) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
... 10 more
[2023-05-24T11:29:34,166][INFO ][org.logstash.beats.BeatsHandler][main][94a21e8610243f7243e86939f98b4336f15d3e1f1870b94ddd975b461d051b1a] [local: 0:0:0:0:0:0:0:1:5044, remote: 0:0:0:0:0:0:0:1:62431] Handling exception: io.netty.handler.codec.DecoderException: org.logstash.beats.InvalidFrameProtocolException: Invalid version of beats protocol: 3 (caused by: org.logstash.beats.InvalidFrameProtocolException: Invalid version of beats protocol: 3)
[2023-05-24T11:29:34,166][WARN ][io.netty.channel.DefaultChannelPipeline][main][94a21e8610243f7243e86939f98b4336f15d3e1f1870b94ddd975b461d051b1a] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
io.netty.handler.codec.DecoderException: org.logstash.beats.InvalidFrameProtocolException: Invalid version of beats protocol: 3
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:499) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:426) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:393) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:376) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:305) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.AbstractChannelHandlerContext.access$300(AbstractChannelHandlerContext.java:61) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final] at io.netty.channel.AbstractChannelHandlerContext$4.run(AbstractChannelHandlerContext.java:286) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:66) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.87.Final.jar:4.1.87.Final]
at java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: org.logstash.beats.InvalidFrameProtocolException: Invalid version of beats protocol: 3
at org.logstash.beats.Protocol.version(Protocol.java:22) ~[logstash-input-beats-6.5.0.jar:?]
at org.logstash.beats.BeatsParser.decode(BeatsParser.java:62) ~[logstash-input-beats-6.5.0.jar:?]
at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:529) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:468) ~[netty-codec-4.1.87.Final.jar:4.1.87.Final]
... 12 more
By the way, here’s my new config of Filebeat and Logstash :
logstash.conf file :
input {
beats {
port => 5044
}
}
filter {
# Add any desired filters for processing your logs
}
output {
opensearch {
hosts => ["https://localhost:9200"]
index => "filebeat-%{+YYYY.MM.dd}"
user => "admin"
password => "admin"
ssl => true
ssl_certificate_verification => false
cacert => "path/to/root-ca.pem"
}
}
And my filebeat.yml file :
###################### Filebeat Configuration Example #########################
# This file is an example configuration file highlighting only the most common
# options. The filebeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/filebeat/index.html
# For more available modules and options, please see the filebeat.reference.yml sample
# configuration file.
# ============================== Filebeat inputs ===============================
filebeat.inputs:
# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.
# filestream is an input for collecting log messages from files.
- type: log
# Unique ID among all inputs, an ID is required.
id: my-log-id
# Change to true to enable this input configuration.
enabled: true
# Paths that should be crawled and fetched. Glob based paths.
paths:
- C:\workspace\demo\report-logs.log
#- c:\programdata\elasticsearch\logs\*
# Exclude lines. A list of regular expressions to match. It drops the lines that are
# matching any regular expression from the list.
# Line filtering happens after the parsers pipeline. If you would like to filter lines
# before parsers, use include_message parser.
#exclude_lines: ['^DBG']
# Include lines. A list of regular expressions to match. It exports the lines that are
# matching any regular expression from the list.
# Line filtering happens after the parsers pipeline. If you would like to filter lines
# before parsers, use include_message parser.
#include_lines: ['^ERR', '^WARN']
# Exclude files. A list of regular expressions to match. Filebeat drops the files that
# are matching any regular expression from the list. By default, no files are dropped.
#prospector.scanner.exclude_files: ['.gz$']
# Optional additional fields. These fields can be freely picked
# to add additional information to the crawled log files for filtering
#fields:
# level: debug
# review: 1
# ============================== Filebeat modules ==============================
filebeat.config.modules:
# Glob pattern for configuration loading
path: ${path.config}/modules.d/*.yml
# Set to true to enable config reloading
reload.enabled: false
# Period on which files under path should be checked for changes
#reload.period: 10s
# ======================= Elasticsearch template setting =======================
setup.template.settings:
index.number_of_shards: 1
#index.codec: best_compression
#_source.enabled: false
# ================================== General ===================================
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:
# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]
# Optional fields that you can specify to add additional information to the
# output.
#fields:
# env: staging
# ================================= Dashboards =================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false
# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:
# =================================== Kibana ===================================
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:
# Kibana Host
# Scheme and port can be left out and will be set to the default (http and 5601)
# In case you specify and additional path, the scheme is required: http://localhost:5601/path
# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
host: "localhost:5601"
# Kibana Space ID
# ID of the Kibana Space into which the dashboards should be loaded. By default,
# the Default Space will be used.
#space.id:
# =============================== Elastic Cloud ================================
# These settings simplify using Filebeat with the Elastic Cloud (https://cloud.elastic.co/).
# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:
# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:
# ================================== Outputs ===================================
# Configure what output to use when sending the data collected by the beat.
# ---------------------------- Elasticsearch Output ----------------------------
#output.elasticsearch:
# Array of hosts to connect to.
#hosts: ["localhost:9200"]
# Protocol - either `http` (default) or `https`.
#protocol: "http"
# Authentication credentials - either API key or username/password.
#api_key: "id:api_key"
#username: "admin"
#password: "admin"
# ------------------------------ Logstash Output -------------------------------
output.logstash:
# The Logstash hosts
hosts: ["localhost:5044"]
# Optional SSL. By default is off.
# List of root certificates for HTTPS server verifications
ssl.certificate_authorities: ["path/to//root-ca.pem"]
# Certificate for SSL client authentication
ssl.certificate: "path/to/client.pem"
# Client Certificate Key
ssl.key: "path/to/client-key.pem"
# ================================= Processors =================================
processors:
- add_host_metadata:
when.not.contains.tags: forwarded
- add_cloud_metadata: ~
- add_docker_metadata: ~
- add_kubernetes_metadata: ~
# ================================== Logging ===================================
# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug
# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publisher", "service".
#logging.selectors: ["*"]
# ============================= X-Pack Monitoring ==============================
# Filebeat can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.
# Set to true to enable the monitoring reporter.
#monitoring.enabled: false
# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:
# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:
# ============================== Instrumentation ===============================
# Instrumentation support for the filebeat.
#instrumentation:
# Set to true to enable instrumentation of filebeat.
#enabled: false
# Environment in which filebeat is running on (eg: staging, production, etc.)
#environment: ""
# APM Server hosts to report instrumentation results to.
#hosts:
# - http://localhost:8200
# API Key for the APM Server(s).
# If api_key is set then secret_token will be ignored.
#api_key:
# Secret token for the APM Server(s).
#secret_token:
# ================================= Migration ==================================
# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true
@zakaria This error looks like a Beats - Logstash connectivity issue and not Logstash - OpenSearch.
Since Beats in your config connects to Logstash directly, OpenSearch has nothing to do with this issue.
I’d suggest testing the Logstash and OpenSearch connectivity without the Beats first. Once that is working, you can focus on the Beats to Logstash connection.
Try with log or text files as input in Logstash and check if OpenSearch creates the index. You can find some examples in OpenSearch documentation.
To troubleshoot Beats to Logstash connectivity I’d suggest using Elastic documentation.
Ok. Thank you very much for your help 
!
Hey @zakaria
Just chimming in, What I noticed was your logstash input doesnt match you Filebeat output.
perhaps try something like this since this is internal not sure if you need certifiates for TCP/TLS on localhost/127.0.0.1 && restart service.
Filebeat_config
filebeat.inputs:
- type: log
id: my-log-id
enabled: true
paths:
- - C:\workspace\demo\report-logs.log
filebeat.config.modules:
path: ${path.config}/modules.d/*.yml
reload.enabled: false
output.logstash:
hosts: ["localhost:5044"]
processors:
- add_host_metadata:
when.not.contains.tags: forwarded
- add_cloud_metadata: ~
- add_docker_metadata: ~
- add_kubernetes_metadata: ~
Logstash_config
# Sample Logstash configuration for creating a simple
# Beats -> Logstash -> Elasticsearch pipeline.
input {
beats {
port => 5044
}
}
output {
opensearch {
hosts => ["https://localhost:9200"]
auth_type => {
type => 'basic'
user => 'admin'
password => 'changeit'
}
ecs_compatibility => disabled
ssl => true
cacert => "/opt/logstash-8.6.1/root-ca.pem"
index => "%{[@metadata][beat]}-%{+YYYY.MM.dd}"
}
}
@zakaria
how did you resolved this:
{“type”:“log”,“@timestamp”:“2023-07-12T22:32:51Z”,“tags”:[“error”,“plugins”,“securityDashboards”],“pid”:12627,“message”:“StatusCodeError: Authorization Exception\n at respond (/opt/athena-opendash/node_modules/elasticsearch/src/lib/transport.js:349:15)\n at checkRespForFailure (/opt/athena-opendash/node_modules/elasticsearch/src/lib/transport.js:306:7)\n at HttpConnector. (/opt/athena-opendash/node_modules/elasticsearch/src/lib/connectors/http.js:173:7)\n at IncomingMessage.wrapper (/opt/athena-opendash/node_modules/lodash/lodash.js:4991:19)\n at IncomingMessage.emit (events.js:412:35)\n at IncomingMessage.emit (domain.js:475:12)\n at endReadableNT (internal/streams/readable.js:1333:12)\n at processTicksAndRejections (internal/process/task_queues.js:82:21) {\n status: 403,\n displayName: ‘AuthorizationException’,\n path: ‘/_plugins/_security/tenantinfo’,\n query: {},\n body: undefined,\n statusCode: 403,\n response: ‘’,\n toString: [Function (anonymous)],\n toJSON: [Function (anonymous)]\n}”}
{“type”:“log”,“@timestamp”:“2023-07-12T22:32:51Z”,“tags”:[“warning”,“environment”],“pid”:12627,“message”:“Detected an unhandled Promise rejection.\nAuthorization Exception :: {"path":"/_plugins/_security/tenantinfo","query":{},"statusCode":403,"response":""}”}