On Wed, Jul 31, 2019 at 12:24:58PM -0700, Gordon Messmer wrote:
> On Tuesday, July 30, 2019 22:35 PDT, Sumit Bose wrote:
> >
> > the version of SSSD you are using should automatically pick a new range
> > if the RID is too large. Can you send your sssd.conf for a start to
> > better understand
On Tuesday, July 30, 2019 22:35 PDT, Sumit Bose wrote:
the version of SSSD you are using should automatically pick a new range
if the RID is too large. Can you send your sssd.conf for a start to
better understand your setup and see what might preventing SSSD from
picking a new range?
The
On Tue, Jul 30, 2019 at 01:11:44PM -0700, Gordon Messmer wrote:
> I have what I think is an odd situation. One of the users I support is
> complaining that he is unable to log in to his domain-member Linux system.
> After enabling debug logging, I've found the error "Could not convert
>
This combination also works well on our very large AD:
ldap_idmap_range_min = 20
ldap_idmap_range_max = 200020
ldap_idmap_range_size = 100
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i)
Thanks, it is workning now.
The first value I tried for ldap_idmap_range_size was too high.
I then took the RID which I suppose is the last number in the SID:
340002
and gave it a little higher value
40
Remove /var/lib/sss/db and restart sssd.
On 13 January 2016 at 08:36,
On (12/01/16 14:00), h...@miracle.dk wrote:
>Hi
>
>I have two users in the AD. Only one of them can login with ssh or su on the
>Linux server.
>
>The user admjoin is the one made the "realm join" and he can login:
>/var/log/sssd/sssd_corp.acme.com.log:
>Mapping user [AdmJoin] objectSID
