On 02/02/2016 09:21 AM, Alexander Bokovoy wrote:
On Mon, 01 Feb 2016, Jakub Hrozek wrote:
On Tue, Jan 05, 2016 at 07:55:33PM +0100, Sumit Bose wrote:
Hi,
to find out to which local group a external user is mapped we do a
dereference search over the external groups with the SIDs related to the
On Mon, 01 Feb 2016, Jakub Hrozek wrote:
On Tue, Jan 05, 2016 at 07:55:33PM +0100, Sumit Bose wrote:
Hi,
to find out to which local group a external user is mapped we do a
dereference search over the external groups with the SIDs related to the
external user. If a SID is mapped to more than one
On Tue, Jan 05, 2016 at 07:55:33PM +0100, Sumit Bose wrote:
> Hi,
>
> to find out to which local group a external user is mapped we do a
> dereference search over the external groups with the SIDs related to the
> external user. If a SID is mapped to more than one external group we
> currently con
On Tue, 05 Jan 2016, Sumit Bose wrote:
Hi,
to find out to which local group a external user is mapped we do a
dereference search over the external groups with the SIDs related to the
external user. If a SID is mapped to more than one external group we
currently consider only the first returned m
On 01/05/2016 07:55 PM, Sumit Bose wrote:
Hi,
to find out to which local group a external user is mapped we do a
dereference search over the external groups with the SIDs related to the
external user. If a SID is mapped to more than one external group we
currently consider only the first returne
Hi,
to find out to which local group a external user is mapped we do a
dereference search over the external groups with the SIDs related to the
external user. If a SID is mapped to more than one external group we
currently consider only the first returned match. With this patch all
results are tak