Add TCM LDAP authentication #4468
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vaintrub
approved these changes
Aug 27, 2024
andreyaksenov
approved these changes
Aug 28, 2024
|
|
||
| Enter the LDAP server connection parameters: | ||
|
|
||
| * **Endpoints**. URLs of the LDAP server. |
There was a problem hiding this comment.
It would be convenient to have an example here. So, a user can understand that 127.0.0.1:5056 is enough and the `ldap://`` schema is not required.
| * **Endpoints**. URLs of the LDAP server. | ||
| * **Request timeout**. The timeout for |tcm| requests to the LDAP server, in seconds. | ||
| * **Enabled TLS**. If the server uses LDAPS, turn this toggle on and specify | ||
| TLS connection parameters, such as a certificate and a key file. |
There was a problem hiding this comment.
Maybe, add the Click **Next** ... sentence after the list?
| shown above, it substitutes ``{0}`` with the username part of the email address (before ``@``) | ||
| entered into the login form. For example, the username ``user1@tarantool.io`` | ||
| forms the following DN for bind request: ``cn=user1,cn=users,dc=tarantool,dc=io``. | ||
| - **Template query**. A template for querying the LDAP server for the DN. This |
There was a problem hiding this comment.
Idea: mark such fields with (optional) explicitly (like we do in API docs)
|
|
||
| .. _tcm_ldap_auth_config_disable: | ||
|
|
||
| Disabling LDAP configurations |
There was a problem hiding this comment.
Nit:
Suggested change
| Disabling LDAP configurations | |
| Turning of LDAP configurations |
Co-authored-by: Andrey Aksenov <38073144+andreyaksenov@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #3635
Deployment: https://docs.d.tarantool.io/en/doc/gh-3635-tcm-ldap/tooling/tcm/tcm_access_control/tcm_ldap_auth/