Ability to specify multiple ldap_base for searching [#152927779] #1301
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
Stuart-Johnson
approved these changes
Apr 17, 2018
jleonardw9
approved these changes
Apr 17, 2018
wtholt
approved these changes
Apr 18, 2018
marklohr
approved these changes
Apr 18, 2018
|
This request is very happy making news--was one of the issues we had in our
environment when we started with SPARC way back when-- too many
heterogeneous Active Directories and the gem was unable to deal with them.
…On Tue, Apr 17, 2018 at 11:59 PM, Mark Lohr ***@***.***> wrote:
***@***.**** approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1301 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABWesKpfEDY82eSlRR3AKoiN8tnziZpoks5tprolgaJpZM4TY4L2>
.
|
|
This won’t solve the problem of multiple AD servers. Just multiple OU on the same server. It allows you to search different branches of the tree. I’m sure this could easily be refactored to allow multiple AD servers using a similar method the ldap_host setting.
From: <owner-sparc_request@musc.edu> on behalf of morizono <notifications@github.com>
Reply-To: sparc-request/sparc-request <reply@reply.github.com>
Date: Wednesday, April 18, 2018 at 12:58 AM
To: sparc-request/sparc-request <sparc-request@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [sparc-request/sparc-request] Ability to specify multiple ldap_base for searching [#152927779] (#1301)
This request is very happy making news--was one of the issues we had in our
environment when we started with SPARC way back when-- too many
heterogeneous Active Directories and the gem was unable to deal with them.
On Tue, Apr 17, 2018 at 11:59 PM, Mark Lohr ***@***.***> wrote:
***@***.**** approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1301 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABWesKpfEDY82eSlRR3AKoiN8tnziZpoks5tprolgaJpZM4TY4L2>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#1301 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AH7TzTGn6_lTEUbcySSnQAfe9Gf67NlYks5tpsf2gaJpZM4TY4L2>.
…-------------------------------------------------------------------------
This message was secured via TLS by MUSC.
|
kayla-glick
approved these changes
May 2, 2018
jwiel86
approved these changes
May 8, 2018
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.
This converts the ldap_base setting to a json array and uses that array to search multiple base DN. This will still work with single base DN instances.