add user_format_string to allow use with AD #3067
Open
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.
Description
We encountered issues with LDAP login integration using our Active Directory (AD) when binding with the user_attr format. This update introduces a new
user_format
property in the LDAP configuration. This property accepts a Python format string, which defaults to the previous configuration but allows for custom user string formats.config example:
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Current testing is broken on Caldera(see #3013). But this is being used in production.
Checklist: