I deployed OpenSearch Dashboards based on the helm tutorial.
Based on the doc, the default username admin and password admin.
However, I got error:
What would be the correct default username admin and password admin? Thanks! 
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 to see where you can include extra configuration parameters in your deployment.
Nate
Hi @nateynate thanks for help. After I deploy OpenSearch Dashboards, all I did is updating opensearchHosts and enable ingress:
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:
> > 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"}
1 Like
@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
Hi @nateynate sorry for confusing. 
I mean all logs look good, however, the default username and password do not work.
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, 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!
2 Likes
Now I have more understanding. The default username and password for OpenSearch are actually
username: kibanaserver
password: kibanaserver
instead of
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
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
2 Likes
@tayo Could you open a new thread? Please share the OpenSearch version that you’ve deployed with helm charts.
I believe the issue still exists. I tried both admin:admin and kibanaserver:kibanaserver.
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
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
@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.