* Adds Windows security documentation Signed-off-by: Fanit Kolchina <[email protected]> * Incorporated tech reveiw feedback Signed-off-by: Fanit Kolchina <[email protected]> * Included powershell and removed call Signed-off-by: Fanit Kolchina <[email protected]> * Changed to backslashes Signed-off-by: Fanit Kolchina <[email protected]> * Incorporated doc review feedback Signed-off-by: Fanit Kolchina <[email protected]> * Incorporated editorial feedback Signed-off-by: Fanit Kolchina <[email protected]> Signed-off-by: Fanit Kolchina <[email protected]>
1.6 KiB
1.6 KiB
layout, title, nav_order, has_children, has_toc, redirect_from
| layout | title | nav_order | has_children | has_toc | redirect_from | |
|---|---|---|---|---|---|---|
| default | Configuration | 5 | true | false |
|
Security configuration
The plugin includes demo certificates so that you can get up and running quickly. To use OpenSearch in a production environment, you must configure it manually:
- Replace the demo certificates.
- Reconfigure
opensearch.ymlto use your certificates. - Reconfigure
config.ymlto use your authentication backend (if you don't plan to use the internal user database). - Modify the configuration YAML files.
- If you plan to use the internal user database, set a password policy in
opensearch.yml. - Apply changes using the
securityadminscript. - Start OpenSearch.
- Add users, roles, role mappings, and tenants.
If you don't want to use the plugin, see Disable security.
The security plugin has several default users, roles, action groups, permissions, and settings for OpenSearch Dashboards that use kibana in their names. We will change these names in a future release. {: .note }