Skip to content

Commit 6af6650

Browse files
derek-hoDarshitChanpuraNaarcha-AWSnatebower
authored
Remove admin:admin default and update instructions for demo setup (opensearch-project#5887)
* Update some admin:admin references Signed-off-by: Derek Ho <[email protected]> * Update all references except for helm Signed-off-by: Derek Ho <[email protected]> * Update helm Signed-off-by: Derek Ho <[email protected]> * Reverts changes made to _install-and-configure folder Signed-off-by: Darshit Chanpura <[email protected]> * Apply suggestions from code review Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Derek Ho <[email protected]> * Update _about/quickstart.md Signed-off-by: Naarcha-AWS <[email protected]> * Apply suggestions from code review Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> * Update quickstart.md Signed-off-by: Naarcha-AWS <[email protected]> --------- Signed-off-by: Derek Ho <[email protected]> Signed-off-by: Darshit Chanpura <[email protected]> Signed-off-by: Derek Ho <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> Co-authored-by: Darshit Chanpura <[email protected]> Co-authored-by: Darshit Chanpura <[email protected]> Co-authored-by: Naarcha-AWS <[email protected]> Co-authored-by: Nathan Bower <[email protected]>
1 parent 796008b commit 6af6650

File tree

17 files changed

+54
-52
lines changed

17 files changed

+54
-52
lines changed

‎_about/quickstart.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,9 @@ You'll need a special file, called a Compose file, that Docker Compose uses to d
5252
opensearch-node1 "./opensearch-docker…" opensearch-node1 running 0.0.0.0:9200->9200/tcp, 9300/tcp, 0.0.0.0:9600->9600/tcp, 9650/tcp
5353
opensearch-node2 "./opensearch-docker…" opensearch-node2 running 9200/tcp, 9300/tcp, 9600/tcp, 9650/tcp
5454
```
55-
1. Query the OpenSearch REST API to verify that the service is running. You should use `-k` (also written as `--insecure`) to disable host name checking because the default security configuration uses demo certificates. Use `-u` to pass the default username and password (`admin:admin`).
55+
1. Query the OpenSearch REST API to verify that the service is running. You should use `-k` (also written as `--insecure`) to disable hostname checking because the default security configuration uses demo certificates. Use `-u` to pass the default username and password (`admin:<custom-admin-password>`).
5656
```bash
57-
curl https://localhost:9200 -ku admin:admin
57+
curl https://localhost:9200 -ku admin:<custom-admin-password>
5858
```
5959
Sample response:
6060
```json
@@ -76,7 +76,7 @@ You'll need a special file, called a Compose file, that Docker Compose uses to d
7676
"tagline" : "The OpenSearch Project: https://opensearch.org/"
7777
}
7878
```
79-
1. Explore OpenSearch Dashboards by opening `http://localhost:5601/` in a web browser on the same host that is running your OpenSearch cluster. The default username is `admin` and the default password is `admin`.
79+
1. Explore OpenSearch Dashboards by opening `http://localhost:5601/` in a web browser on the same host that is running your OpenSearch cluster. The default username is `admin` and the default password is set in your `docker-compose.yml` file in the `OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password>` setting.
8080

8181
## Create an index and field mappings using sample data
8282

@@ -100,18 +100,18 @@ Create an index and define field mappings using a dataset provided by the OpenSe
100100
```
101101
1. Define the field mappings with the mapping file.
102102
```bash
103-
curl -H "Content-Type: application/x-ndjson" -X PUT "https://localhost:9200/ecommerce" -ku admin:admin --data-binary "@ecommerce-field_mappings.json"
103+
curl -H "Content-Type: application/x-ndjson" -X PUT "https://localhost:9200/ecommerce" -ku admin:<custom-admin-password> --data-binary "@ecommerce-field_mappings.json"
104104
```
105105
1. Upload the index to the bulk API.
106106
```bash
107-
curl -H "Content-Type: application/x-ndjson" -X PUT "https://localhost:9200/ecommerce/_bulk" -ku admin:admin --data-binary "@ecommerce.json"
107+
curl -H "Content-Type: application/x-ndjson" -X PUT "https://localhost:9200/ecommerce/_bulk" -ku admin:<custom-admin-password> --data-binary "@ecommerce.json"
108108
```
109109
1. Query the data using the search API. The following command submits a query that will return documents where `customer_first_name` is `Sonya`.
110110
```bash
111-
curl -H 'Content-Type: application/json' -X GET "https://localhost:9200/ecommerce/_search?pretty=true" -ku admin:admin -d' {"query":{"match":{"customer_first_name":"Sonya"}}}'
111+
curl -H 'Content-Type: application/json' -X GET "https://localhost:9200/ecommerce/_search?pretty=true" -ku admin:<custom-admin-password> -d' {"query":{"match":{"customer_first_name":"Sonya"}}}'
112112
```
113113
Queries submitted to the OpenSearch REST API will generally return a flat JSON by default. For a human readable response body, use the query parameter `pretty=true`. For more information about `pretty` and other useful query parameters, see [Common REST parameters]({{site.url}}{{site.baseurl}}/opensearch/common-parameters/).
114-
1. Access OpenSearch Dashboards by opening `http://localhost:5601/` in a web browser on the same host that is running your OpenSearch cluster. The default username is `admin` and the default password is `admin`.
114+
1. Access OpenSearch Dashboards by opening `http://localhost:5601/` in a web browser on the same host that is running your OpenSearch cluster. The default username is `admin` and the password is set in your `docker-compose.yml` file in the `OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password>` setting.
115115
1. On the top menu bar, go to **Management > Dev Tools**.
116116
1. In the left pane of the console, enter the following:
117117
```json
@@ -162,4 +162,4 @@ OpenSearch will fail to start if your host's `vm.max_map_count` is too low. Revi
162162
opensearch-node1 | ERROR: [1] bootstrap checks failed
163163
opensearch-node1 | [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
164164
opensearch-node1 | ERROR: OpenSearch did not exit normally - check the logs at /usr/share/opensearch/logs/opensearch-cluster.log
165-
```
165+
```

‎_api-reference/tasks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -267,7 +267,7 @@ To associate requests with tasks for better tracking, you can provide a `X-Opaqu
267267
Usage:
268268
269269
```bash
270-
curl -i -H "X-Opaque-Id: 111111" "https://localhost:9200/_tasks" -u 'admin:admin' --insecure
270+
curl -i -H "X-Opaque-Id: 111111" "https://localhost:9200/_tasks" -u 'admin:<custom-admin-password>' --insecure
271271
```
272272
{% include copy.html %}
273273
@@ -326,6 +326,6 @@ content-length: 768
326326
This operation supports the same parameters as the `tasks` operation. The following example shows how you can associate `X-Opaque-Id` with specific tasks:
327327
328328
```bash
329-
curl -i -H "X-Opaque-Id: 123456" "https://localhost:9200/_tasks?nodes=opensearch-node1" -u 'admin:admin' --insecure
329+
curl -i -H "X-Opaque-Id: 123456" "https://localhost:9200/_tasks?nodes=opensearch-node1" -u 'admin:<custom-admin-password>' --insecure
330330
```
331331
{% include copy.html %}

‎_benchmark/quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ After installation, you can verify OpenSearch is running by going to `localhost:
3131
Use the following command to verify OpenSearch is running with SSL certificate checks disabled:
3232

3333
```bash
34-
curl -k -u admin:admin https://localhost:9200 # the "-k" option skips SSL certificate checks
34+
curl -k -u admin:<custom-admin-password> https://localhost:9200 # the "-k" option skips SSL certificate checks
3535

3636
{
3737
"name" : "147ddae31bf8.opensearch.org",

‎_clients/javascript/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ To connect to the default OpenSearch host, create a client object with the addre
4848
var host = "localhost";
4949
var protocol = "https";
5050
var port = 9200;
51-
var auth = "admin:admin"; // For testing only. Don't store credentials in code.
51+
var auth = "admin:<custom-admin-password>"; // For testing only. Don't store credentials in code.
5252
var ca_certs_path = "/full/path/to/root-ca.pem";
5353

5454
// Optional client certificates if you don't want to use HTTP basic authentication.
@@ -360,7 +360,7 @@ The following sample program creates a client, adds an index with non-default se
360360
var host = "localhost";
361361
var protocol = "https";
362362
var port = 9200;
363-
var auth = "admin:admin"; // For testing only. Don't store credentials in code.
363+
var auth = "admin:<custom-admin-password>"; // For testing only. Don't store credentials in code.
364364
var ca_certs_path = "/full/path/to/root-ca.pem";
365365

366366
// Optional client certificates if you don't want to use HTTP basic authentication.

‎_monitoring-your-cluster/pa/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -245,7 +245,7 @@ curl -XPOST http://localhost:9200/_plugins/_performanceanalyzer/rca/cluster/conf
245245
If you encounter the `curl: (52) Empty reply from server` response, run the following command to enable RCA:
246246

247247
```bash
248-
curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
248+
curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:<custom-admin-password>' -k
249249
```
250250

251251
### Example API query and response

‎_observing-your-data/log-ingestion.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ This should result in a single document being written to the OpenSearch cluster
6363
Run the following command to see one of the raw documents in the OpenSearch cluster:
6464

6565
```bash
66-
curl -X GET -u 'admin:admin' -k 'https://localhost:9200/apache_logs/_search?pretty&size=1'
66+
curl -X GET -u 'admin:<custom-admin-password>' -k 'https://localhost:9200/apache_logs/_search?pretty&size=1'
6767
```
6868

6969
The response should show the parsed log data:

‎_observing-your-data/trace/getting-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ node-0.example.com | [2020-11-19T16:29:55,267][INFO ][o.e.c.m.MetadataMappingSe
7676
In a new terminal window, run the following command to see one of the raw documents in the OpenSearch cluster:
7777

7878
```bash
79-
curl -X GET -u 'admin:admin' -k 'https://localhost:9200/otel-v1-apm-span-000001/_search?pretty&size=1'
79+
curl -X GET -u 'admin:<custom-admin-password>' -k 'https://localhost:9200/otel-v1-apm-span-000001/_search?pretty&size=1'
8080
```
8181

8282
Navigate to `http://localhost:5601` in a web browser and choose **Trace Analytics**. You can see the results of your single click in the Jaeger HotROD web interface: the number of traces per API and HTTP method, latency trends, a color-coded map of the service architecture, and a list of trace IDs that you can use to drill down on individual operations.

‎_reporting/rep-cli-env-var.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Values from the command line argument have higher priority than the environment
3030
The following command requests a report with basic authentication in PNG format:
3131

3232
```
33-
opensearch-reporting-cli --url https://localhost:5601/app/dashboards#/view/7adfa750-4c81-11e8-b3d7-01146121b73d --format png --auth basic --credentials admin:admin
33+
opensearch-reporting-cli --url https://localhost:5601/app/dashboards#/view/7adfa750-4c81-11e8-b3d7-01146121b73d --format png --auth basic --credentials admin:<custom-admin-password>
3434
```
3535

3636
Upon success, the report will download to the current directory.

‎_search-plugins/sql/sql/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ POST _plugins/_sql
6161
To run the preceding query in the command line, use the [curl](https://curl.haxx.se/) command:
6262

6363
```bash
64-
curl -XPOST https://localhost:9200/_plugins/_sql -u 'admin:admin' -k -H 'Content-Type: application/json' -d '{"query": "SELECT * FROM my-index* LIMIT 50"}'
64+
curl -XPOST https://localhost:9200/_plugins/_sql -u 'admin:<custom-admin-password>' -k -H 'Content-Type: application/json' -d '{"query": "SELECT * FROM my-index* LIMIT 50"}'
6565
```
6666
{% include copy.html %}
6767

‎_security/access-control/cross-cluster-search.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,7 @@ services:
7777
- discovery.type=single-node
7878
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
7979
- "OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
80+
- "OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password>" # The initial admin password used by the demo configuration
8081
ulimits:
8182
memlock:
8283
soft: -1
@@ -97,6 +98,7 @@ services:
9798
- discovery.type=single-node
9899
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
99100
- "OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
101+
- "OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password>" # The initial admin password used by the demo configuration
100102
ulimits:
101103
memlock:
102104
soft: -1
@@ -120,13 +122,13 @@ networks:
120122
After the clusters start, verify the names of each:
121123

122124
```json
123-
curl -XGET -u 'admin:admin' -k 'https://localhost:9200'
125+
curl -XGET -u 'admin:<custom-admin-password>' -k 'https://localhost:9200'
124126
{
125127
"cluster_name" : "opensearch-ccs-cluster1",
126128
...
127129
}
128130
129-
curl -XGET -u 'admin:admin' -k 'https://localhost:9250'
131+
curl -XGET -u 'admin:<custom-admin-password>' -k 'https://localhost:9250'
130132
{
131133
"cluster_name" : "opensearch-ccs-cluster2",
132134
...
@@ -154,7 +156,7 @@ docker inspect --format='{% raw %}{{range .NetworkSettings.Networks}}{{.IPAddres
154156
On the coordinating cluster, add the remote cluster name and the IP address (with port 9300) for each "seed node." In this case, you only have one seed node:
155157

156158
```json
157-
curl -k -XPUT -H 'Content-Type: application/json' -u 'admin:admin' 'https://localhost:9250/_cluster/settings' -d '
159+
curl -k -XPUT -H 'Content-Type: application/json' -u 'admin:<custom-admin-password>' 'https://localhost:9250/_cluster/settings' -d '
158160
{
159161
"persistent": {
160162
"cluster.remote": {
@@ -169,13 +171,13 @@ curl -k -XPUT -H 'Content-Type: application/json' -u 'admin:admin' 'https://loca
169171
On the remote cluster, index a document:
170172

171173
```bash
172-
curl -XPUT -k -H 'Content-Type: application/json' -u 'admin:admin' 'https://localhost:9200/books/_doc/1' -d '{"Dracula": "Bram Stoker"}'
174+
curl -XPUT -k -H 'Content-Type: application/json' -u 'admin:<custom-admin-password>' 'https://localhost:9200/books/_doc/1' -d '{"Dracula": "Bram Stoker"}'
173175
```
174176

175177
At this point, cross-cluster search works. You can test it using the `admin` user:
176178

177179
```bash
178-
curl -XGET -k -u 'admin:admin' 'https://localhost:9250/opensearch-ccs-cluster1:books/_search?pretty'
180+
curl -XGET -k -u 'admin:<custom-admin-password>' 'https://localhost:9250/opensearch-ccs-cluster1:books/_search?pretty'
179181
{
180182
...
181183
"hits": [{
@@ -192,8 +194,8 @@ curl -XGET -k -u 'admin:admin' 'https://localhost:9250/opensearch-ccs-cluster1:b
192194
To continue testing, create a new user on both clusters:
193195

194196
```bash
195-
curl -XPUT -k -u 'admin:admin' 'https://localhost:9200/_plugins/_security/api/internalusers/booksuser' -H 'Content-Type: application/json' -d '{"password":"password"}'
196-
curl -XPUT -k -u 'admin:admin' 'https://localhost:9250/_plugins/_security/api/internalusers/booksuser' -H 'Content-Type: application/json' -d '{"password":"password"}'
197+
curl -XPUT -k -u 'admin:<custom-admin-password>' 'https://localhost:9200/_plugins/_security/api/internalusers/booksuser' -H 'Content-Type: application/json' -d '{"password":"password"}'
198+
curl -XPUT -k -u 'admin:<custom-admin-password>' 'https://localhost:9250/_plugins/_security/api/internalusers/booksuser' -H 'Content-Type: application/json' -d '{"password":"password"}'
197199
```
198200

199201
Then run the same search as before with `booksuser`:
@@ -218,8 +220,8 @@ curl -XGET -k -u booksuser:password 'https://localhost:9250/opensearch-ccs-clust
218220
Note the permissions error. On the remote cluster, create a role with the appropriate permissions, and map `booksuser` to that role:
219221

220222
```bash
221-
curl -XPUT -k -u 'admin:admin' -H 'Content-Type: application/json' 'https://localhost:9200/_plugins/_security/api/roles/booksrole' -d '{"index_permissions":[{"index_patterns":["books"],"allowed_actions":["indices:admin/shards/search_shards","indices:data/read/search"]}]}'
222-
curl -XPUT -k -u 'admin:admin' -H 'Content-Type: application/json' 'https://localhost:9200/_plugins/_security/api/rolesmapping/booksrole' -d '{"users" : ["booksuser"]}'
223+
curl -XPUT -k -u 'admin:<custom-admin-password>' -H 'Content-Type: application/json' 'https://localhost:9200/_plugins/_security/api/roles/booksrole' -d '{"index_permissions":[{"index_patterns":["books"],"allowed_actions":["indices:admin/shards/search_shards","indices:data/read/search"]}]}'
224+
curl -XPUT -k -u 'admin:<custom-admin-password>' -H 'Content-Type: application/json' 'https://localhost:9200/_plugins/_security/api/rolesmapping/booksrole' -d '{"users" : ["booksuser"]}'
223225
```
224226

225227
Both clusters must have the user, but only the remote cluster needs the role and mapping; in this case, the coordinating cluster handles authentication (i.e. "Does this request include valid user credentials?"), and the remote cluster handles authorization (i.e. "Can this user access this data?").

‎_security/access-control/impersonation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,5 +47,5 @@ plugins.security.authcz.impersonation_dn:
4747
To impersonate another user, submit a request to the system with the HTTP header `opendistro_security_impersonate_as` set to the name of the user to be impersonated. A good test is to make a GET request to the `_plugins/_security/authinfo` URI:
4848

4949
```bash
50-
curl -XGET -u 'admin:admin' -k -H "opendistro_security_impersonate_as: user_1" https://localhost:9200/_plugins/_security/authinfo?pretty
50+
curl -XGET -u 'admin:<custom-admin-password>' -k -H "opendistro_security_impersonate_as: user_1" https://localhost:9200/_plugins/_security/authinfo?pretty
5151
```

‎_troubleshoot/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ If you run legacy Kibana OSS scripts against OpenSearch Dashboards---for example
3030
In this case, your scripts likely include the `"kbn-xsrf: true"` header. Switch it to the `osd-xsrf: true` header:
3131

3232
```
33-
curl -XPOST -u 'admin:admin' 'https://DASHBOARDS_ENDPOINT/api/saved_objects/_import' -H 'osd-xsrf:true' --form [email protected]
33+
curl -XPOST -u 'admin:<custom-admin-password>' 'https://DASHBOARDS_ENDPOINT/api/saved_objects/_import' -H 'osd-xsrf:true' --form [email protected]
3434
```
3535

3636

‎_tuning-your-cluster/availability-and-recovery/remote-store/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ curl -X POST "https://localhost:9200/_remotestore/_restore" -H 'Content-Type: ap
8686
**Restore all shards of a given index**
8787

8888
```bash
89-
curl -X POST "https://localhost:9200/_remotestore/_restore?restore_all_shards=true" -ku admin:admin -H 'Content-Type: application/json' -d'
89+
curl -X POST "https://localhost:9200/_remotestore/_restore?restore_all_shards=true" -ku admin:<custom-admin-password> -H 'Content-Type: application/json' -d'
9090
{
9191
"indices": ["my-index"]
9292
}

‎_tuning-your-cluster/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ less /var/log/opensearch/opensearch-cluster.log
177177
Perform the following `_cat` query on any node to see all the nodes formed as a cluster:
178178

179179
```bash
180-
curl -XGET https://<private-ip>:9200/_cat/nodes?v -u 'admin:admin' --insecure
180+
curl -XGET https://<private-ip>:9200/_cat/nodes?v -u 'admin:<custom-admin-password>' --insecure
181181
```
182182

183183
```

‎_tuning-your-cluster/replication-plugin/auto-follow.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Replication rules are a collection of patterns that you create against a single
2828
Create a replication rule on the follower cluster:
2929

3030
```bash
31-
curl -XPOST -k -H 'Content-Type: application/json' -u 'admin:admin' 'https://localhost:9200/_plugins/_replication/_autofollow?pretty' -d '
31+
curl -XPOST -k -H 'Content-Type: application/json' -u 'admin:<custom-admin-password>' 'https://localhost:9200/_plugins/_replication/_autofollow?pretty' -d '
3232
{
3333
"leader_alias" : "my-connection-alias",
3434
"name": "my-replication-rule",
@@ -46,13 +46,13 @@ If the Security plugin is disabled, you can leave out the `use_roles` parameter.
4646
To test the rule, create a matching index on the leader cluster:
4747

4848
```bash
49-
curl -XPUT -k -H 'Content-Type: application/json' -u 'admin:admin' 'https://localhost:9201/movies-0001?pretty'
49+
curl -XPUT -k -H 'Content-Type: application/json' -u 'admin:<custom-admin-password>' 'https://localhost:9201/movies-0001?pretty'
5050
```
5151

5252
And confirm its replica shows up on the follower cluster:
5353

5454
```bash
55-
curl -XGET -u 'admin:admin' -k 'https://localhost:9200/_cat/indices?v'
55+
curl -XGET -u 'admin:<custom-admin-password>' -k 'https://localhost:9200/_cat/indices?v'
5656
```
5757

5858
It might take several seconds for the index to appear.
@@ -67,7 +67,7 @@ yellow open movies-0001 kHOxYYHxRMeszLjTD9rvSQ 1 1 0
6767
To retrieve a list of existing replication rules that are configured on a cluster, send the following request:
6868

6969
```bash
70-
curl -XGET -u 'admin:admin' -k 'https://localhost:9200/_plugins/_replication/autofollow_stats'
70+
curl -XGET -u 'admin:<custom-admin-password>' -k 'https://localhost:9200/_plugins/_replication/autofollow_stats'
7171

7272
{
7373
"num_success_start_replication": 1,
@@ -96,7 +96,7 @@ curl -XGET -u 'admin:admin' -k 'https://localhost:9200/_plugins/_replication/aut
9696
To delete a replication rule, send the following request to the follower cluster:
9797

9898
```bash
99-
curl -XDELETE -k -H 'Content-Type: application/json' -u 'admin:admin' 'https://localhost:9200/_plugins/_replication/_autofollow?pretty' -d '
99+
curl -XDELETE -k -H 'Content-Type: application/json' -u 'admin:<custom-admin-password>' 'https://localhost:9200/_plugins/_replication/_autofollow?pretty' -d '
100100
{
101101
"leader_alias" : "my-conection-alias",
102102
"name": "my-replication-rule"

0 commit comments

Comments
 (0)