Hello, I’m having trouble deploying an Opensearch 2.0.0 cluster with the security plugin enabled. When deploying it in this way I get the following error: [2022-06-02T16:21:38,726][WARN ][o.o.d.HandshakingTransportAddressConnector] [DNS] handshake failed for [connectToRemoteMasterNode[IP:9300]] o…

@vsgoncalo Please check this link. [image] Securityadmin.sh uses http port 9200 and not transport port 9300 in OpenSearch 2.0.0 Security @asfoorial As per the release notes of version 2.0 the TransportClient authentication/authorisation have been removed. Tha…

I have the same issue, The answer from @pablo is not helpful for me I do not have an issue with securityadmin.sh my issue si that nides just do not form cluster. Nodes do not connect, when i dislable security it works as expected. @vsgoncalo have you been able to solve this?

Hi @Marek1 , I believe I had a similar issue to yours and the answer from @pablo did not work for me either. I was eventually able to solve it. Unfortunately I’m not exactly sure what did the trick but I think that the problem was that I was using the absolute paths to the certificates in the config…

@vsgoncalo @pablo Mine certs are directly in config dir and so my paths are only certs file names. Like this: plugins.security.disabled: false plugins.security.ssl.transport.pemcert_filepath: cert.pem plugins.security.ssl.transport.pemkey_filepath : cert.key plugins.security.ssl.transport.pe…

You have a typo on “plugins.security.ssl.http.enabked: true”. Could that be the cause of the error? Also, I think you need to set the “plugins.security.nodes_dn” config as well.

Thansk for pointing out but it was just rewrite issue because my nodes are not connected to the internet and I can not copy-paste configs. Just question do I really need to run securityadmin.sh before i run OpenSearch every time I change opensearch,yml?

No need. I just launched each node with the correct configs and it ended up working.

@Marek1 @vsgoncalo The info provided previously, regards deprecation of Transport Client authentication/authorization. Port 9300 will be still in use for transport traffic. This affects your deployment too. Once you disable demo certificates and you’ll use custom TLS certificates, you’ll need to ad…

@pablo Oke so I have the following config, but still errors like: Caused by: org.opensearch.OpenSearchException: Transport client authentication no longer supported. I also tried transport.tcp.port: 9200 plugins.security.ssl.transport.enabled: “false” plugins.security.nodes_dn: - ‘subject= CN=op…

@Raki ‘subject=’ is not a part of the certificate DN. Generate certificates Generate certificates Try the below instead. plugins.security.authcz.admin_dn: - 'CN=ADMIN,OU=DSH Cert Auth,O=DSH' plugins.security.nodes_dn: - 'CN=opensearch,O…

"Transport Client Authentication no longer supported" error when deploying cluster with security plugin enabled

Security

pablo June 2, 2022, 9:06pm 2

@vsgoncalo Please check this link.

Topic		Replies	Views
"Transport client authentication no longer supported" in between-node transport layer communication Security troubleshoot , configure	6	1660	December 13, 2023
OpenSearchException: Transport client authentication no longer supported Security troubleshoot , configure	2	2726	November 9, 2022
Have a problem to enable security OpenSearch discuss , troubleshoot , configure , install	6	1651	November 28, 2023
Security transport config for 2.0.0 Security troubleshoot , install	13	2184	December 12, 2022
SSL Error unable to configure Opensearch Cluster in 6 VMs Security troubleshoot , configure	14	1787	March 8, 2023

"Transport Client Authentication no longer supported" error when deploying cluster with security plugin enabled

Related topics