AUTH_LDAP_BIND_AS_AUTHENTICATING_USER is now loaded from environment #779
Conversation
This file contains 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
|
Hi, |
|
The default value for this parameter in |
|
@tobiasge I agree :) |
|
@tobiasge do you approve the modification? |
tobiasge
approved these changes
Sep 21, 2022
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.
Related Issue: #690
New Behavior
Providing AUTH_LDAP_BIND_AS_AUTHENTICATING_USER environment variable, Netbox container binds to LDAP server using username and password provided by the user being authenticated.
Contrast to Current Behavior
Currently, as described in issue #690 this parameter is not taken into account.
Discussion: Benefits and Drawbacks
No service user/password are needed.
Changes to the Wiki
N/A
Proposed Release Note Entry
Fix: It is now possible to bind Netbox container to LDAP server using user login/password.
Double Check
developbranch.