Standalone Operation of mender-connect

General Discussions
1

The documentation (and configuration) of mender-connect suggests that it can be used without the full mender-client and that it only requires mender-authd. Is this correct?

mender-authd and mender-connect both seem to run, but they never connect to hosted.mender.io. Trace logs are shown below.

$mender-auth --log-level trace daemon
record_id=1 severity=trace time="2024-May-10 10:44:54.566023" name="Global" msg="Loading the keystore" 
record_id=2 severity=trace time="2024-May-10 10:44:54.566099" name="Global" msg="Loading private key" 
record_id=3 severity=info time="2024-May-10 10:44:54.568848" name="Global" msg="Successfully loaded private key from /var/lib/mender/mender-agent.pem" 
record_id=4 severity=info time="2024-May-10 10:44:54.571210" name="Global" msg="The authentication daemon is now ready to accept incoming authentication request" 

$mender-connect --trace daemon
INFO[2024-05-10T10:45:23-04:00] Loaded configuration file: /etc/mender/mender-connect.conf 
WARN[2024-05-10T10:45:23-04:00] ShellArguments is empty, defaulting to [--login] 
TRAC[2024-05-10T10:45:23-04:00] daemon Run starting                          
TRAC[2024-05-10T10:45:23-04:00] mender-connect connecting to dbus            
TRAC[2024-05-10T10:45:23-04:00] mender-connect entering main loop.           
TRAC[2024-05-10T10:45:23-04:00] messageLoop: starting                        
TRAC[2024-05-10T10:45:23-04:00] messageLoop: posting event: reconnect-req; waiting for response 
TRAC[2024-05-10T10:45:23-04:00] needsReconnect: got event: reconnect-req     
TRAC[2024-05-10T10:45:23-04:00] dbusEventLoop: daemon needs to reconnect     
TRAC[2024-05-10T10:45:33-04:00] dbusEventLoop: WaitForJwtTokenStateChange [], err timeout waiting for signal JwtTokenStateChange 
TRAC[2024-05-10T10:45:44-04:00] dbusEventLoop: WaitForJwtTokenStateChange [], err timeout waiting for signal JwtTokenStateChange 
TRAC[2024-05-10T10:45:56-04:00] dbusEventLoop: WaitForJwtTokenStateChange [], err timeout waiting for signal JwtTokenStateChange 
TRAC[2024-05-10T10:46:07-04:00] dbusEventLoop: WaitForJwtTokenStateChange [], err timeout waiting for signal JwtTokenStateChange 
TRAC[2024-05-10T10:46:18-04:00] dbusEventLoop: WaitForJwtTokenStateChange [], err timeout waiting for signal JwtTokenStateChange 
TRAC[2024-05-10T10:46:29-04:00] dbusEventLoop: WaitForJwtTokenStateChange [], err timeout waiting for signal JwtTokenStateChange 
TRAC[2024-05-10T10:46:40-04:00] dbusEventLoop: WaitForJwtTokenStateChange [], err timeout waiting for signal JwtTokenStateChange 
TRAC[2024-05-10T10:46:51-04:00] dbusEventLoop: WaitForJwtTokenStateChange [], err timeout waiting for signal JwtTokenStateChange 
TRAC[2024-05-10T10:47:02-04:00] dbusEventLoop: WaitForJwtTokenStateChange [], err timeout waiting for signal JwtTokenStateChange

Is there a missing parameter in the config?

$cat /etc/mender/mender-connect.conf
{
  "ShellCommand": "/bin/bash",
  "User": "root",
  "MenderClient": {
    "Disable": true
  }
}