**Previous step:** https://github.com/tarantool/doc/issues/3945 **Feedback:** https://github.com/tarantool/doc/issues/3959 **Product:** Tarantool **Since:** 3.0 **Root document:** https://www.tarantool.io/en/enterprise_doc/security/ **SME:** @ Totktonada # Details Currently, `box.cfg` examples are used. P.S. Some environment variables should also be updated ([comparison table](https://docs.google.com/spreadsheets/d/1_yEK9N_hBVWIga9mOk7zZzA6Zd3mAq7e5KZsnrbgj30/edit#gid=0)). # Main steps - [ ] Create the `Connections` topic in the [Configuration](https://www.tarantool.io/en/doc/latest/concepts/configuration/) section (see also [Connections and Authentication](https://www.postgresql.org/docs/current/runtime-config-connection.html)). The structure of this topic might be: - Overview (iproto, connectors, replication, sharding) - Listen URI (ip+port, unix socket) - Advertise URI (domain names can be used) - SSL (`Traffic encryption` will be moved here, mention certificate reloading) - [ ] Create the `Authentication` topic in the `Configuration` section and move the info from the [Access control](https://www.tarantool.io/en/doc/latest/enterprise/security/#access-control) section. - Add corresponding options to reference.