kadmin unit tests

[Kevin Coffman]

Thanks, I figured this out after sending the original message.  The
kpasswd_port was specified in the kdc.conf.proto, but the
krb5.conf.proto needed the kpasswd_server specification with the port
number, otherwise kpasswd still tried port 464.

BTW, I changed the "#if 0" to "#if 1" around the pw_min_life check in
kadm5_chpass_principal_3 and the "too soon" test runs correctly.  I
don't understand the history/reasoning behind moving the check, so I
don't know if that is the correct solution or not.

K.C.

-----Original Message-----
From: Ezra Peisach [mailto:epeisach at MIT.EDU] 
Sent: Wednesday, January 22, 2003 5:14 PM
To: Kevin Coffman
Cc: krbdev at MIT.EDU
Subject: Re: kadmin unit tests


You do not need to rely on port 464 as far as I know. kadmind will
listen 
on the kadmind_port and kpasswd_port stanzas from kdc.conf.

For the client - you can specify kpasswd_server - with a port number -
in
krb5.conf.

In fact - the dejagnu test suite does this already....

	Ezra