Is the above (securityadmin.sh using 9200 by default) is an intended behaviour or it is just the documentation needs to be updated? I have scripts that run the above code and set the port using “-p 9300” and it used to work on 1.3.2 but failed on 2.0.0.
@asfoorial As per the release notes of version 2.0 the TransportClient authentication/authorisation have been removed.
That has affected the way the securityadmin.sh communicates with the cluster. Now securityadmin.sh requires HTTP connection - port 9200.
The documentation still refers to the old configuration. It will be reported to the dev team.
Hello everyone, I’m stuck, if someone can help me that would be great !
When I disable install demo config and point transport and http to my certs, I get an error “Transport client authentication no longer supported”
When I add enabled: falseto security.ssl.transport, I get an error “plugins.security.ssl.transport.enabled must be set to ‘true’”
When i remove every security.ssl.transport lines, I get an error “plugins.security.ssl.transport.keystore_filepath or plugins.security.ssl.transport.server.pemcert_filepath and plugins.security.ssl.transport.client.pemcert_filepath must be set if transport ssl is requested.”