A Linux Agent fails to initialize or hangs when configured with an invalid agent name containing special characters (e.g., &) or escaped sequences (e.g., \\0). The agent proceeds to certificate handling before validating the name, leading to inconsistent behavior.
Symptoms The agent log shows the following sequence:
U00011649 Invalid host name: 'NAME', valid characters: A-Z 0-9 _.$@-#U02000297 Agent doesn't have valid certificate, requesting new one from server.U00045014 Exception 'java.lang.IllegalArgumentException: "improperly specified input name: CN=NAME\0NULL, OU=TEST, C=US"' at 'javax.security.auth.x500.X500Principal.()'.
U00045015 The previous error was caused by 'java.io.IOException: "escaped hex value must include two valid digits"'
The agent-side validation currently only checks for name length. Detailed character validation is performed by the JCP after the connection and certificate request sequence has already initiated.
Ensure the agent name in the .ini file adheres to the documented naming rules (A-Z, 0-9, _, ., $, @, -, #) and does not exceed 32 characters.
Handling invalid agent names consistently is currently under review by Engineering (DE209459).