Skip to content

[Config] Update the 'Security hardening guide' to using a new config #3665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks
Tracked by #3957
andreyaksenov opened this issue Sep 1, 2023 · 1 comment · Fixed by #3985 or #3991
Closed
2 tasks
Tracked by #3957

[Config] Update the 'Security hardening guide' to using a new config #3665

andreyaksenov opened this issue Sep 1, 2023 · 1 comment · Fixed by #3985 or #3991
Assignees
Labels
3.0 config EE EE functionality

Comments

@andreyaksenov
Copy link
Contributor

andreyaksenov commented Sep 1, 2023

Previous step: #3945
Feedback: #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).

Main steps

  • Create the Connections topic in the Configuration section (see also Connections and Authentication). 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 section.
    • Add corresponding options to reference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0 config EE EE functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant