KDC 1.15.1 - addprinc random failure
Yegui Cai
caiyegui at gmail.com
Sat Feb 2 09:36:32 EST 2019
Hi all.
I just found out that the issue was caused by some race conditions when I
experiment with master-master deployment. Please ignore this thread.
Cheers,
Yegui
On Fri, Feb 1, 2019 at 11:20 AM Yegui Cai <caiyegui at gmail.com> wrote:
> Hi all.
>
> I run KDC 1.15.1. At the host, I use kadmin.local to add a principle. Very
> strange that my first attempt failed silently while the second attempt
> succeeded. Here are the steps:
>
> [root at gamma-hactive ~]# kadmin.local
> Authenticating as principal hdfs/admin at EXAMPLE.COM with password.
> kadmin.local: addprinc yegui
> WARNING: no policy specified for yegui at EXAMPLE.COM; defaulting to no
> policy
> Enter password for principal "yegui at EXAMPLE.COM":
> Re-enter password for principal "yegui at EXAMPLE.COM":
> Principal "yegui at EXAMPLE.COM" created.
> kadmin.local: getprinc yegui
> get_principal: Principal does not exist while retrieving "
> yegui at EXAMPLE.COM".
> kadmin.local: addprinc yegui
> WARNING: no policy specified for yegui at EXAMPLE.COM; defaulting to no
> policy
> Enter password for principal "yegui at EXAMPLE.COM":
> Re-enter password for principal "yegui at EXAMPLE.COM":
> Principal "yegui at EXAMPLE.COM" created.
> kadmin.local: getprinc yegui
> Principal: yegui at EXAMPLE.COM
> Expiration date: [never]
> Last password change: Fri Feb 01 16:00:09 UTC 2019
> Password expiration date: [never]
> Maximum ticket life: 1 day 00:00:00
> Maximum renewable life: 7 days 00:00:00
> Last modified: Fri Feb 01 16:00:09 UTC 2019 (hdfs/admin at EXAMPLE.COM)
> Last successful authentication: [never]
> Last failed authentication: [never]
> Failed password attempts: 0
> Number of keys: 4
> Key: vno 1, aes256-cts-hmac-sha1-96
> Key: vno 1, aes128-cts-hmac-sha1-96
> Key: vno 1, des3-cbc-sha1
> Key: vno 1, arcfour-hmac
> MKey: vno 1
> Attributes: REQUIRES_PRE_AUTH
> Policy: [none]
>
> Any idea? Thanks!
> Yegui
>
More information about the Kerberos
mailing list