Searched hist:f17bb68b5a2d095b69b9e951aa10c6b366b7a7ce (Results 1 – 4 of 4) sorted by relevance
| /plugin/pureldap/lang/en/ |
| H A D | settings.php | f17bb68b5a2d095b69b9e951aa10c6b366b7a7ce Wed Jul 28 12:53:28 UTC 2021 Andreas Gohr <andi@splitbrain.org> new approach for recursive groups
Instead of implementing the recursion client side, we ask the AD server
to resolve nested group memberships for us. This saves potentially many
network requests but may have performance penalties on the AD server
side. However it ensures, we can't make a mistake and thus makes our
code safer to run - also turns out my first attempt was checking nested
groups backwards.
See https://stackoverflow.com/q/40024425 for more discussions on
performance for this.
A config option allows to use the former much faster approach for setups
without nested groups.
Still to do: supporting user lookups by group this way.
|
| /plugin/pureldap/conf/ |
| H A D | default.php | f17bb68b5a2d095b69b9e951aa10c6b366b7a7ce Wed Jul 28 12:53:28 UTC 2021 Andreas Gohr <andi@splitbrain.org> new approach for recursive groups
Instead of implementing the recursion client side, we ask the AD server
to resolve nested group memberships for us. This saves potentially many
network requests but may have performance penalties on the AD server
side. However it ensures, we can't make a mistake and thus makes our
code safer to run - also turns out my first attempt was checking nested
groups backwards.
See https://stackoverflow.com/q/40024425 for more discussions on
performance for this.
A config option allows to use the former much faster approach for setups
without nested groups.
Still to do: supporting user lookups by group this way.
|
| H A D | metadata.php | f17bb68b5a2d095b69b9e951aa10c6b366b7a7ce Wed Jul 28 12:53:28 UTC 2021 Andreas Gohr <andi@splitbrain.org> new approach for recursive groups
Instead of implementing the recursion client side, we ask the AD server
to resolve nested group memberships for us. This saves potentially many
network requests but may have performance penalties on the AD server
side. However it ensures, we can't make a mistake and thus makes our
code safer to run - also turns out my first attempt was checking nested
groups backwards.
See https://stackoverflow.com/q/40024425 for more discussions on
performance for this.
A config option allows to use the former much faster approach for setups
without nested groups.
Still to do: supporting user lookups by group this way.
|
| /plugin/pureldap/classes/ |
| H A D | ADClient.php | f17bb68b5a2d095b69b9e951aa10c6b366b7a7ce Wed Jul 28 12:53:28 UTC 2021 Andreas Gohr <andi@splitbrain.org> new approach for recursive groups
Instead of implementing the recursion client side, we ask the AD server
to resolve nested group memberships for us. This saves potentially many
network requests but may have performance penalties on the AD server
side. However it ensures, we can't make a mistake and thus makes our
code safer to run - also turns out my first attempt was checking nested
groups backwards.
See https://stackoverflow.com/q/40024425 for more discussions on
performance for this.
A config option allows to use the former much faster approach for setups
without nested groups.
Still to do: supporting user lookups by group this way.
|