On 05.04.2021 08:19, Orion Poplawski wrote:
> On 3/23/21 12:09 AM, Konstantin Boyandin via CentOS wrote:
>> Hello,
>>
>> I joined a CentOS 8 box to an AD, using the below document as general
>> guide:
>>
>>
On 3/23/21 12:09 AM, Konstantin Boyandin via CentOS wrote:
Hello,
I joined a CentOS 8 box to an AD, using the below document as general
guide:
On Apr 4, 2021, at 14:08, Gordon Messmer wrote:
>> $ cat /etc/krb5.conf
>> [libdefaults]
>> default_ccache_name = KEYRING:persistent:%{uid}
>
> Specifically, I thought that sssd defaults to KCM storage for kerberos
> credentials, not the kernel keyring. You might be seeing an SELinux
> deny
On Mon, Mar 22, 2021 at 11:10 PM Konstantin Boyandin via CentOS
wrote:
> I joined a CentOS 8 box to an AD, using the below document as general
> guide:
How general? Can you describe what you've done that differed from the guide?
> When I comment a line in /etc/pam.d/password-auth (the one
Hi Konstantin,
Debugging login issues between SSD, PAM, and AD is not for the faint of
heart. In my case I set up Samba 4.3 as a primary AD DC. I could login
with Windows 10 guests but not C8.
I just did the following.
1. I spun up a fresh C8 VM, did not add any users, selected a graphical
Do I understand correctly that this problem
- is too trivial
- isn't in fact CentOS-related
- never happened to anyone else ?
There are no good explanations as far as I see, to such PAM behavior. I
would appreciate advice on where else to ask about this (the mentioned
quick fix doesn't look too
Hello,
I joined a CentOS 8 box to an AD, using the below document as general
guide:
7 matches
Mail list logo
