# Securityadmin.sh uses http port 9200 and not transport port 9300 in OpenSearch 2.0.0

**URL:** <https://forum.opensearch.org/t/securityadmin-sh-uses-http-port-9200-and-not-transport-port-9300-in-opensearch-2-0-0/9760>\
**Category:** Security\
**Tags:** troubleshoot, upgrade\
**Created:** [May 31, 2022, 5:50am UTC](https://forum.opensearch.org/t/securityadmin-sh-uses-http-port-9200-and-not-transport-port-9300-in-opensearch-2-0-0/9760 "2022-05-31T05:50:22Z")\
**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:** [May 31, 2022, 7:31pm UTC](https://forum.opensearch.org/t/securityadmin-sh-uses-http-port-9200-and-not-transport-port-9300-in-opensearch-2-0-0/9760/2 "2022-05-31T19:31:42Z")

</div>

@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/opensearch-build/blob/main/release-notes/opensearch-release-notes-2.0.0.md>

[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/securityadmin-sh-uses-http-port-9200-and-not-transport-port-9300-in-opensearch-2-0-0/9760)._
