Although the java.security.krb5.kdc/realm system properties are able to
override the values inside krb5.conf, it is better to write one without
realm/kdc info at all. So, instead of
60 KDC.saveConfig(KRB5_CONF_FILENAME, kdc, "max_retries = 1");
How about just manually write
Files.write(Paths.get(KRB5_CONF_FILENAME), Arrays.asList(
"[libdefaults]",
"max_retries = 1"));
--Max
On 07/18/2015 01:51 AM, Artem Smotrakov wrote:
Hi Max,
Please see an updated webrev:
http://cr.openjdk.java.net/~asmotrak/8075297/webrev.03/
Artem
On 07/16/2015 11:31 PM, Wang Weijun wrote:
I think it it enough to add a "max_retries = 1" to [libdefaults] of
krb5.conf, and left default timeout value for the test. Please take a
look at updated webrev:
http://cr.openjdk.java.net/~asmotrak/8075297/webrev.02/
Can you also add the same line to the krb5.conf for the other test?
Thanks
Max