On Tue, Sep 20, 2016 at 02:03:38PM +, Larry Rosen wrote:
> Thanks, that explains a lot (I didn't catch the difference in auth services).
> Would this be mitigated by putting sss in front of files in nsswitch.conf)?
>
> /etc/nsswitchconf:
> passwd: files sss
> shadow: files sss
>
<jhro...@redhat.com>
To: freeipa-users@redhat.com
Subject: Re: [Freeipa-users] login auth fails then success
Message-ID: <20160918201459.uhijnc4gyfykgzic@hendrix>
Content-Type: text/plain; charset=us-ascii
On Fri, Sep 16, 2016 at 06:23:03PM +, Larry Rosen wrote:
> Sorry I thoug
ar users and then pam_sss succeeds. I
wonder if the best way to deal with the log messages is just to
configure logrotate a bit more aggressively?
>
> -Original Message-
> From: Rob Crittenden [mailto:rcrit...@redhat.com]
> Sent: Friday, September 16, 2016 1:39 PM
> To: Larry
Message-
From: Rob Crittenden [mailto:rcrit...@redhat.com]
Sent: Friday, September 16, 2016 1:39 PM
To: Larry Rosen <larry.ro...@jdrsolutions.com>; freeipa-users@redhat.com
Subject: Re: [Freeipa-users] login auth fails then success
Larry Rosen wrote:
> We have a web app that logs in using
Larry Rosen wrote:
We have a web app that logs in using a service (automated login user,
non-expiring, non-failure count) account that leaves these log entries
all day long. This does not appear to cause any problems, it just make
my logs grow unnecessarily and creates a lot of noise in the
We have a web app that logs in using a service (automated login user,
non-expiring, non-failure count) account that leaves these log entries all day
long. This does not appear to cause any problems, it just make my logs grow
unnecessarily and creates a lot of "noise" in the log.
Any ideas why
