2021-02-22 17:27:13 +05:30
---
2022-07-23 23:45:48 +05:30
stage: Systems
2021-02-22 17:27:13 +05:30
group: Distribution
2022-05-07 20:08:51 +05:30
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments"
2021-02-22 17:27:13 +05:30
type: reference
---
2021-03-11 19:13:27 +05:30
# Encrypted Configuration **(FREE SELF)**
2021-02-22 17:27:13 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/45712) in GitLab 13.7.
GitLab can read settings for certain features from encrypted settings files. The supported features are:
2022-07-16 23:28:13 +05:30
- [LDAP `bind_dn` and `password` ](auth/ldap/index.md#use-encrypted-credentials ).
2021-11-11 11:23:49 +05:30
- [SMTP `user_name` and `password` ](raketasks/smtp.md#secrets ).
2021-02-22 17:27:13 +05:30
2022-08-13 15:12:31 +05:30
To enable the encrypted configuration settings, a new base key must be generated for
2021-02-22 17:27:13 +05:30
`encrypted_settings_key_base` . The secret can be generated in the following ways:
**Omnibus Installation**
2022-08-13 15:12:31 +05:30
Starting with 13.7 the new secret is automatically generated for you, but you must ensure your
2021-02-22 17:27:13 +05:30
`/etc/gitlab/gitlab-secrets.json` contains the same values on all nodes.
**GitLab Cloud Native Helm Chart**
Starting with GitLab 13.7, the new secret is automatically generated if you have the `shared-secrets` chart enabled. Otherwise, you need
to follow the [secrets guide for adding the secret ](https://docs.gitlab.com/charts/installation/secrets.html#gitlab-rails-secret ).
**Source Installation**
The new secret can be generated by running:
```shell
bundle exec rake gitlab:env:info RAILS_ENV=production GITLAB_GENERATE_ENCRYPTED_SETTINGS_KEY_BASE=true
```
2021-11-11 11:23:49 +05:30
This prints general information on the GitLab instance, but also causes the key to be generated in `<path-to-gitlab-rails>/config/secrets.yml` .
