[SSSD-users] Re: [AD] User discovery/enumeration issue due to domain settings

2019-07-30 Thread Christian Lamparter
Hello again, On Fri, 2019-07-26 at 14:08 +0200, Jakub Hrozek wrote: > On Fri, Jul 26, 2019 at 12:50:16PM +0200, Christian Lamparter wrote: > > I'm currently setting up sssd (Debian 1.16.3) on Debian Buster 10.0 > > and I ran into a problem that I was able to trace dow

[SSSD-users] Re: [AD] User discovery/enumeration issue due to domain settings

2019-08-06 Thread Christian Lamparter
On Wed, 2019-07-31 at 09:26 +0200, Jakub Hrozek wrote: > On Tue, Jul 30, 2019 at 06:42:06PM +0200, Christian Lamparter wrote: > > On Fri, 2019-07-26 at 14:08 +0200, Jakub Hrozek wrote: > > > On Fri, Jul 26, 2019 at 12:50:16PM +0200, Christian Lamparter wrote: > > > >

[SSSD-users] [AD] User discovery/enumeration issue due to domain settings

2019-07-26 Thread Christian Lamparter
Hello Folks, I'm currently setting up sssd (Debian 1.16.3) on Debian Buster 10.0 and I ran into a problem that I was able to trace down to the domain permission/security settings that placed the users into a special OU that machine accounts can't read. First a bit of background: Currently,

[SSSD-users] Re: How to have a dynamic ldap_default_bind_dn value in sssd.conf?

2019-12-06 Thread Christian Lamparter
On the 2019-11-25 at 11:41 Oscar Torrente wrote: Ok. So what you suggest is applying an ACI to all needed attributes for all users/groups nodes in LDAP directory to give this special account the read permission over them , isn't? I should obfuscate its password in sssd.conf file, though, but