Thanks, here is the key and server config information. I've included the link to the full log of errors and documentation below.
Our implementation currently uses ASCII keys, and follows the 'optional' usage for ASCII (Per the man page for chrony.conf :
"
The key can be specified as a string of ASCII characters not containing white space with an optional ASCII: prefix, or...".
Thanks for the heads up, I will take a closer look and add keys with additional lengths and formats, and then retest. We really need to test against implicit ASCII, explicit ASCII, and explicit HEX keys. Our test plans do need to expand to cover both ASCII and HEX key usage/support, being honest, so if this is an aspect we need to address, we can definitely do so.
Chrony Client :
/etc/chrony.conf :
server 10.207.4.84 prefer version 4 iburst key 20
20 SHA1 421b67770525bde2e926354a88ae2f81c7c76108
NTP Server :
/etc/ntp.conf :
keys /etc/ntp.keys
trustedkey 1 5 20 21 22
/etc/ntp.keys:
20 SHA1 421b67770525bde2e926354a88ae2f81c7c76108 #RSA-SHA1-compliant
-Mike