[31814] in Kerberos
Re: principal: Invalid argument while creating "foo@FOO".
daemon@ATHENA.MIT.EDU (Tom Yu)
Mon Dec 28 21:41:52 2009
To: Jeff Blaine <jblaine@kickflop.net>
From: Tom Yu <tlyu@mit.edu>
Date: Mon, 28 Dec 2009 21:41:27 -0500
In-Reply-To: <4B3964AC.6070105@kickflop.net> (Jeff Blaine's message of "Mon,
28 Dec 2009 21:08:44 -0500")
Message-ID: <ldvtyvabiy0.fsf@cathode-dark-space.mit.edu>
MIME-Version: 1.0
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
Jeff Blaine <jblaine@kickflop.net> writes:
> No, that works fine.
When running kadmin remotely, does "addprinc" without "-randkey"
succeed?
> On 12/28/2009 9:03 PM, Tom Yu wrote:
>> Jeff Blaine<jblaine@kickflop.net> writes:
>>
>>> Still very very stumped. Any ideas? Anyone?
>>>
>>> -randkey is not accepted at all
>>>
>>> [root@mega ~]# kadmin -p admin/admin
>>> Authenticating as principal admin/admin with password.
>>> Password for admin/admin@FOO:
>>> kadmin: getprinc foo
>>> get_principal: Principal does not exist while retrieving "foo@FOO".
>>> kadmin: addprinc -randkey foo
>>> WARNING: no policy specified for foo@FOO; defaulting to no policy
>>> add_principal: Invalid argument while creating "foo@FOO".
>>> kadmin: quit
>>
>> Do you get the same behavior running kadmin.local on the KDC?
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
