Here's weirdness for you. I left yesterday and it wasn't working. I
arrived this morning and it was. Near as I can tell, it had to do with
the sssd cache.
Another user had a similar problem when I unenrolled & enrolled his
system to the new servers. It wouldn't take any of his passwords (he
I don’t think it is, actually. That’s just where we left off. I’ll start
walking more logs this week.
Bret Wortman
Founder, Damascus Products LLC
855-644-2783 | b...@damascusproducts.com
http://damascusproducts.com/
10332 Main St Suite 319 Fairfax, VA 22030
On Jun 3, 2018, 3:00 PM -0400, Jakub
> On 3 Jun 2018, at 13:33, Bret Wortman via FreeIPA-users
> wrote:
>
> I just realized that I never closed the loop on this problem and just
> finished upgrading all my systems to use our new IPA servers. And this
> problem is still with me.
>
> I can log onto some workstations but not
I just realized that I never closed the loop on this problem and just
finished upgrading all my systems to use our new IPA servers. And this
problem is still with me.
I can log onto some workstations but not all. My only enabled hbac rule
is still "allow_all", and it's as permissive as it
Back to this thread; I stood up a new VM and used ipa-client-install to
subscribe it to the new server. I can log on to it from both ssh and
console, so the problem on my original workstation appears to be in
switching from one server to another.
Thoughts?
On 02/21/2018 10:29 AM, Bret
