# What are the correct default username and password for OpenSearch Dashboards?

**URL:** <https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970>\
**Category:** OpenSearch Dashboards\
**Tags:** troubleshoot\
**Created:** [March 21, 2022, 11:35pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970 "2022-03-21T23:35:12Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hongbo-Miao](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/hongbo-miao/32/2831_2.png) [@Hongbo-Miao](https://forum.opensearch.org/u/Hongbo-Miao)\
**Post date:** [March 21, 2022, 11:35pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/1 "2022-03-21T23:35:13Z")

</div>

I deployed OpenSearch Dashboards based on the [helm tutorial](https://opensearch.org/docs/latest/dashboards/install/helm/).

Based on [the doc](https://opensearch.org/docs/latest/dashboards/index/), the default username `admin` and password `admin`.  
However, I got error:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/7/7e4b4a7aaa3b89f9896a9984e7ca53b26742b669.png)

What would be the correct default username `admin` and password `admin`? Thanks! 😃

---

<div class="post-metadata">

**Author:** ![nateynate](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/nateynate/32/4913_2.png) [@nateynate](https://forum.opensearch.org/u/nateynate)\
**Post date:** [March 22, 2022, 7:43pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/2 "2022-03-22T19:43:38Z")

</div>

Hi @Hongbo-Miao!

Sorry to hear you’re having trouble. I’m afraid I’m not 100% intimate with helm. Were there any log entries that indicated a particular security index didn’t get initialized? Any other errors that stand out to you?

It doesn’t look like you’ve done anything wrong here. `admin:admin` is correct for a new cluster that hasn’t had auth configured, so I suspect something might have been misconfigured.

I do know that there are some configuration entries you can add to define those default accounts. You might be able to follow some of the guidance in [helm-charts/README.md at main · opensearch-project/helm-charts · GitHub](https://github.com/opensearch-project/helm-charts/blob/main/README.md) to see where you can include extra configuration parameters in your deployment.

Nate

---

<div class="post-metadata">

**Author:** ![Hongbo-Miao](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/hongbo-miao/32/2831_2.png) [@Hongbo-Miao](https://forum.opensearch.org/u/Hongbo-Miao)\
**Post date:** [March 22, 2022, 8:58pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/3 "2022-03-22T20:58:37Z")

</div>

Hi @nateynate thanks for help. After I deploy OpenSearch Dashboards, all I did is updating `opensearchHosts` and enable `ingress`:

```nohighlight
opensearchHosts: "https://my-opensearch.example.com:9200"

ingress:
  enabled: true
  annotations: {}
  hosts:
    - host: my-opensearch-dashboards.example.com
      paths:
        - path: /
          backend:
            serviceName: opensearch-dashboards
            servicePort: 5601
  tls: []

```

The log looks all good:

```nohighlight
> > kubectl logs opensearch-dashboards-xxx -n=my-namespace
{"type":"log","@timestamp":"2022-03-22T20:46:07Z","tags":["info","plugins-service"],"pid":1,"message":"Plugin \"visTypeXy\" is disabled."}
{"type":"log","@timestamp":"2022-03-22T20:46:08Z","tags":["warning","config","deprecation"],"pid":1,"message":"\"cpu.cgroup.path.override\" is deprecated and has been replaced by \"ops.cGroupOverrides.cpuPath\""}
{"type":"log","@timestamp":"2022-03-22T20:46:08Z","tags":["warning","config","deprecation"],"pid":1,"message":"\"cpuacct.cgroup.path.override\" is deprecated and has been replaced by \"ops.cGroupOverrides.cpuAcctPath\""}
{"type":"log","@timestamp":"2022-03-22T20:46:09Z","tags":["info","plugins-system"],"pid":1,"message":"Setting up [44] plugins: [alertingDashboards,usageCollection,opensearchDashboardsUsageCollection,opensearchDashboardsLegacy,mapsLegacy,share,opensearchUiShared,embeddable,legacyExport,expressions,data,home,console,apmOss,management,indexPatternManagement,advancedSettings,savedObjects,securityDashboards,reportsDashboards,indexManagementDashboards,anomalyDetectionDashboards,dashboard,visualizations,visTypeVega,visTypeTable,visTypeTimeline,timeline,visTypeMarkdown,tileMap,regionMap,inputControlVis,ganttChartDashboards,visualize,queryWorkbenchDashboards,charts,visTypeVislib,visTypeTimeseries,visTypeTagcloud,visTypeMetric,observabilityDashboards,discover,savedObjectsManagement,bfetch]"}
{"type":"log","@timestamp":"2022-03-22T20:46:14Z","tags":["info","savedobjects-service"],"pid":1,"message":"Waiting until all OpenSearch nodes are compatible with OpenSearch Dashboards before starting saved objects migrations..."}
{"type":"log","@timestamp":"2022-03-22T20:46:15Z","tags":["info","savedobjects-service"],"pid":1,"message":"Starting saved objects migrations"}
{"type":"log","@timestamp":"2022-03-22T20:46:15Z","tags":["info","plugins-system"],"pid":1,"message":"Starting [44] plugins: [alertingDashboards,usageCollection,opensearchDashboardsUsageCollection,opensearchDashboardsLegacy,mapsLegacy,share,opensearchUiShared,embeddable,legacyExport,expressions,data,home,console,apmOss,management,indexPatternManagement,advancedSettings,savedObjects,securityDashboards,reportsDashboards,indexManagementDashboards,anomalyDetectionDashboards,dashboard,visualizations,visTypeVega,visTypeTable,visTypeTimeline,timeline,visTypeMarkdown,tileMap,regionMap,inputControlVis,ganttChartDashboards,visualize,queryWorkbenchDashboards,charts,visTypeVislib,visTypeTimeseries,visTypeTagcloud,visTypeMetric,observabilityDashboards,discover,savedObjectsManagement,bfetch]"}
{"type":"log","@timestamp":"2022-03-22T20:46:19Z","tags":["listening","info"],"pid":1,"message":"Server running at http://0.0.0.0:5601"}
{"type":"log","@timestamp":"2022-03-22T20:46:21Z","tags":["info","http","server","OpenSearchDashboards"],"pid":1,"message":"http server running at http://0.0.0.0:5601"}

```

---

<div class="post-metadata">

**Author:** ![nateynate](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/nateynate/32/4913_2.png) [@nateynate](https://forum.opensearch.org/u/nateynate)\
**Post date:** [March 24, 2022, 2:56pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/4 "2022-03-24T14:56:04Z")

</div>

@Hongbo-Miao that’s awesome! I’m glad you got it working. Please accept my genuine extra thank you to you for coming back to share your solution with everyone.

Nate

---

<div class="post-metadata">

**Author:** ![Hongbo-Miao](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/hongbo-miao/32/2831_2.png) [@Hongbo-Miao](https://forum.opensearch.org/u/Hongbo-Miao)\
**Post date:** [March 26, 2022, 2:15am UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/5 "2022-03-26T02:15:37Z")

</div>

Hi @nateynate sorry for confusing. 😅  
I mean all logs look good, however, the default username and password do not work.

---

<div class="post-metadata">

**Author:** ![Hongbo-Miao](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/hongbo-miao/32/2831_2.png) [@Hongbo-Miao](https://forum.opensearch.org/u/Hongbo-Miao)\
**Post date:** [April 25, 2022, 9:12pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/7 "2022-04-25T21:12:57Z")

</div>

I found the username and password to sign in OpenSearch Dashboards are the ones used to connect OpenSearch.

In this case, to connect my OpenSearch [https://my-opensearch.example.com:9200](https://my-opensearch.example.com:9200), I have a pair of username and password for Basic Auth.

So that is also the pair of username and password to sign in OpenSearch Dashboards. So basically OpenSearch Dashboards do not hold its own secrets.

Hope it helps future people!

---

<div class="post-metadata">

**Author:** ![Hongbo-Miao](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/hongbo-miao/32/2831_2.png) [@Hongbo-Miao](https://forum.opensearch.org/u/Hongbo-Miao)\
**Post date:** [June 16, 2022, 6:54pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/8 "2022-06-16T18:54:27Z")

</div>

Now I have more understanding. The default username and password for OpenSearch are actually

```auto
username: kibanaserver
password: kibanaserver

```

instead of

```auto
username: admin
password: admin

```

I think the document need update.

Also, if you set different username and password and removed default username and password for OpenSearch, for OpenSearch Dashboards, you can pass

```auto
OPENSEARCH_USERNAME=xxx
OPENSEARCH_PASSWORD=xxx

```

as environments.

More info is at [Waiting until all OpenSearch nodes are compatible with OpenSearch Dashboards before starting saved objects migrations - #2 by Hongbo-Miao](https://forum.opensearch.org/t/waiting-until-all-opensearch-nodes-are-compatible-with-opensearch-dashboards-before-starting-saved-objects-migrations/9959/2)

---

<div class="post-metadata">

**Author:** ![nateynate](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/nateynate/32/4913_2.png) [@nateynate](https://forum.opensearch.org/u/nateynate)\
**Post date:** [July 18, 2022, 3:52pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/9 "2022-07-18T15:52:24Z")

</div>

Thank you so much for the contribution, @Hongbo-Miao!

---

<div class="post-metadata">

**Author:** ![tayo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/tayo/32/6855_2.png) [@tayo](https://forum.opensearch.org/u/tayo)\
**Post date:** [February 2, 2024, 10:11am UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/10 "2024-02-02T10:11:22Z")

</div>

i experienced the same problem too. What is the cause of this?

 ![Screenshot 2024-02-02 at 17.11.10](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/4/4a71448361486539a9ee7dce4b4e2203b090e2df.png)

---

<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:** [February 29, 2024, 9:55pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/11 "2024-02-29T21:55:33Z")

</div>

@tayo Could you open a new thread? Please share the OpenSearch version that you’ve deployed with helm charts.

---

<div class="post-metadata">

**Author:** ![danngyn](https://avatars.discourse-cdn.com/v4/letter/d/2bfe46/32.png) [@danngyn](https://forum.opensearch.org/u/danngyn)\
**Post date:** [March 2, 2024, 9:53pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/12 "2024-03-02T21:53:11Z")

</div>

I believe the issue still exists. I tried both `admin:admin` and `kibanaserver:kibanaserver`.

---

<div class="post-metadata">

**Author:** ![Chris1](https://avatars.discourse-cdn.com/v4/letter/c/ac91a4/32.png) [@Chris1](https://forum.opensearch.org/u/Chris1)\
**Post date:** [March 15, 2024, 2:10pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/13 "2024-03-15T14:10:06Z")

</div>

I have the same issue with the tar balls. Just extract it, disabled the security plugin in opensearch because of certifiactes, chance https to http inside the dashboard config. Both admin:admin and kibanaserver:kibanaserver doesn’t work

---

<div class="post-metadata">

**Author:** ![Chris1](https://avatars.discourse-cdn.com/v4/letter/c/ac91a4/32.png) [@Chris1](https://forum.opensearch.org/u/Chris1)\
**Post date:** [March 15, 2024, 2:28pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/14 "2024-03-15T14:28:29Z")

</div>

I think my problem was that i disabled my security plugin in opensearch, but the dashboard needs in in terms of authentification. Thus, the only possibilities are to enable security in opensearch again or disable security in dashboard either. Second approach worked: [Disabling security - OpenSearch Documentation](https://opensearch.org/docs/latest/security/configuration/disable/)

---

<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:** [March 21, 2024, 1:08am UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/15 "2024-03-21T01:08:27Z")

</div>

@Chris1 The OpenSearch Dashboards security plugin works together with the OpenSearch security plugin.  
All security settings, including users, are located in the OpenSearch security index and managed by the OpenSearch security plugin. OpenSearch Dashboards security plugin makes requests to OpenSearch security plugin during authentication and authorization as it doesn’t maintain its users.

---

<div class="post-metadata">

**Author:** ![nateynate](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/nateynate/32/4913_2.png) [@nateynate](https://forum.opensearch.org/u/nateynate)\
**Post date:** [January 29, 2025, 7:28pm UTC](https://forum.opensearch.org/t/what-are-the-correct-default-username-and-password-for-opensearch-dashboards/8970/16 "2025-01-29T19:28:37Z")

</div>

Just to follow up here, it looks like on Feb 20 2024, just before these postings, when OpenSearch 2.12 was released it required that an environment variable was set (`OPENSEARCH_INITIAL_ADMIN_PASSWORD`) that sets the initial admin password when you deploy your cluster. If these issues occurred on 2.12, that’s likely why the admin password was behaving strangely. Set that variable in your environment prior to deployment and the admin password will be set as such.