TomK via FreeIPA-users wrote:
> Hey Guy's,
>
> Getting below message which in turn fails to list proper UID / GID on
> NFSv4 mounts from within an unprivileged account. All files show up with
> owner and group as nobody / nobody when viewed from the client.
>
> Is there a way to structure
TomK wrote:
> On 3/7/2018 1:11 PM, Rob Crittenden wrote:
> Hey Rob,
>
> When starting idmapd or stopping it, logs on the LDAP server don't
> change. But UID and GID's change to nfsnobody when I set Nobody-User
> and Nobody-Group to nfsnobody in /etc/idmapd.conf .
I don'
TomK wrote:
> On 3/12/2018 11:25 AM, Rob Crittenden wrote:
>> TomK wrote:
>>> On 3/7/2018 1:11 PM, Rob Crittenden wrote:
>>> Hey Rob,
>>>
>>> When starting idmapd or stopping it, logs on the LDAP server don't
>>> change. But UID and GID's cha
TomK wrote:
> On 3/15/2018 11:06 AM, Rob Crittenden wrote:
>> TomK wrote:
>>> On 3/12/2018 11:25 AM, Rob Crittenden wrote:
>>>> TomK wrote:
>>>>> On 3/7/2018 1:11 PM, Rob Crittenden wrote:
>>>>> Hey Rob,
>>>>>
>>&g
I'm trying to get a multi-threaded PAM app working to log in users using
the 'login' service to generate client load:
https://github.com/freeipa/freeipa-perftest/blob/master/src/pamtest.c
The load is generated by running multiple client VMs and on each client
running the pam tester with multiple
> Am Mon, Jan 24, 2022 at 01:36:28PM -0500 schrieb Rob Crittenden:
>
> Hi,
>
> the PAM_PERM_DENIED error is returned from the backend. Please check the
> backend log and krb5_child.log. I agree that it looks a bit like a
> timeout issue since the default krb5_auth_time
cc'ing the sssd users list.
rob
lejeczek via FreeIPA-users wrote:
> Hi guys.
>
> One of the masters started recently to find SSSD dead and says the
> killer is the WATCHDOG - but I'm not sure about that.
> From sssd.log:
> ...
> ** BACKTRACE DUMP ENDS HERE
>
