Using the security API instead of securityadmin.sh in OpenSearch 2.0.0

Hi all,

As several members have reported in the forum and in github that they are having issues running securityadmin.sh due to the removal of TransportClient in 2.x, I would like to ask the following question:

Can we rely on the security API as a replacement for securityadmin.sh. Is there any security functionality that cannot be done in the API but can in securityadmin.sh?

Thanks

@asfoorial securityadmin.sh is using port 9200 in version 2.0.x.
As per documentation, it is recommended to use securityadmin.sh instead of direct REST API calls.