Thanks for helping out Lukas.
Kinit resolves to dc02 then fails pre-authentication because it was not the
master KDC, after providing password, then resolves to dc01 and then gets the
policy rejects again. Tried a few times and it seems that it does not matter
which server it resolves, get
On (02/02/17 19:55), Gilbert, Sonia wrote:
>No. Also they said that they opened up the firewall for all the ports.
>
>[root@server01 /]# kinit 018...@abc.com
>Password for 018...@abc.com:
>kinit: KDC policy rejects request while getting initial credentials
>
>Could it be trying to use
No. Also they said that they opened up the firewall for all the ports.
[root@server01 /]# kinit 018...@abc.com
Password for 018...@abc.com:
kinit: KDC policy rejects request while getting initial credentials
Could it be trying to use krb5.keytab? Is it unique to each instance. Since
it was
In a scenario in which an sssd node joined to Active Directory crashed and had
to be rebuilt, restoring key files from backup, other than the obvious files in
/etc (for krb5, sssd, nss etc.) are there other sssd/krb5 persistent databases
(/var/lib/sss/db ?) that would have to be restored (ctdb
On Wed, Feb 01, 2017 at 08:06:53PM +, Gilbert, Sonia wrote:
> Can't open the bug. I get the following error.
>
> "You are not authorized to access bug #1293168.
>
> Most likely the bug has been restricted for internal development processes
> and we cannot grant access.
>
> If you are a
