argonaut issueshttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues2024-02-16T14:50:49Zhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5458Argonaut client silently dies when Argonaut-Server SSL CA is wrong using https2024-02-16T14:50:49ZjbecotArgonaut client silently dies when Argonaut-Server SSL CA is wrong using httpsHello,
Setup :
Argonaut-server configured with https.
Argonaut-server configured to use a registered certificate but the root CA does not include the intermediate certification chain.
Argonaut-client configured to use https.
Argonaut-c...Hello,
Setup :
Argonaut-server configured with https.
Argonaut-server configured to use a registered certificate but the root CA does not include the intermediate certification chain.
Argonaut-client configured to use https.
Argonaut-client configured to use a registered certficate, and its rootCA includes the intermediate certification chain.
Bug :
Launching a DNS Zone Refresh from FD gives a 500 error (expected). But argonaut-client silently fails and stops. No trace in the log file, no error displayed when launched with -X option.
Solution:
Using the same rootCA including the chain in argonaut-server config works fine.Argonaut 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/4629Better handling of timeouts2024-02-16T14:48:08ZCôme ChillietBetter handling of timeoutsIt seems argonaut client timeout is 10 in JSON::RPC::Client code and we can’t change it.
We should find a way to change this and make sure client timeout is always longer than server timeout.
Argonaut server state cache may be activated...It seems argonaut client timeout is 10 in JSON::RPC::Client code and we can’t change it.
We should find a way to change this and make sure client timeout is always longer than server timeout.
Argonaut server state cache may be activated again thanks to these changes (see #2426 )Argonaut 1.4bmortierbmortier