feat (auth/ldap): support for new ldap fields #453
Merged
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
louisruch
requested changes
Sep 12, 2023
jimlambrt
force-pushed
the
jimlambrt-new-auth-ldap-fields
branch
from
628c44a
to
f5f8aaa
Compare
jimlambrt
force-pushed
the
jimlambrt-new-auth-ldap-fields
branch
from
f5f8aaa
to
62efa7f
Compare
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.
support for auth/ldap: maximum_page_size and dereference_aliases
NOTE: this can't be merged until boundary 0.14.0 is released/tagged and boundary along with the API and SDK are updated in this PR.