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

**URL:** <https://forum.opensearch.org/t/transport-client-authentication-no-longer-supported-error-when-deploying-cluster-with-security-plugin-enabled/9814>\
**Category:** Security\
**Tags:** troubleshoot\
**Created:** [June 2, 2022, 4:26pm UTC](https://forum.opensearch.org/t/transport-client-authentication-no-longer-supported-error-when-deploying-cluster-with-security-plugin-enabled/9814 "2022-06-02T16:26:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pablo/32/10363_2.png) [@pablo](https://forum.opensearch.org/u/pablo)\
**Post date:** [June 2, 2022, 9:06pm UTC](https://forum.opensearch.org/t/transport-client-authentication-no-longer-supported-error-when-deploying-cluster-with-security-plugin-enabled/9814/2 "2022-06-02T21:06:09Z")

</div>

@vsgoncalo Please check this link.

> [@Securityadmin.sh uses http port 9200 and not transport port 9300 in OpenSearch 2.0.0](https://forum.opensearch.org/t/securityadmin-sh-uses-http-port-9200-and-not-transport-port-9300-in-opensearch-2-0-0/9760/2):
>
> @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. [https://github.com/opensearch-project/security/pull/1701](https://github.com/opensearch-project/security/pull/1701)

---

_[View the full topic](https://forum.opensearch.org/t/transport-client-authentication-no-longer-supported-error-when-deploying-cluster-with-security-plugin-enabled/9814)._
