You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason setting FDBNetworkOption::FDB_NET_OPTION_TLS_KEY_BYTES and similar TLS_CERT_BYTES, TLS_CA_BYTES seems like does not have any effect. We use fdb_network_set_option() for this matter.
After setting everything we receive transaction timeouts and the following in client logs:
On the other hand setting environment variables FDB_TLS_CERTIFICATE_FILE, FDB_TLS_KEY_FILE, FDB_TLS_CA_FILE with the paths to the files with same content does the trick and everything works.
We've also tried setting FDBNetworkOption::FDB_NET_OPTION_TLS_KEY_PATH and other _PATH options with no effect as well.
Environment:
FDB 7.1.51
Client in Docker container Linux c31802bb42bc 6.5.0-17-generic #17-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 11 14:01:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered:
The route cause is that setup was called before setting the options.
But one thing is still confusing - how we managed to apply those settings at some point and successfully access FDB while setup-set_network_option order was incorrect.
Hi!
For some reason setting
FDBNetworkOption::FDB_NET_OPTION_TLS_KEY_BYTES
and similarTLS_CERT_BYTES
,TLS_CA_BYTES
seems like does not have any effect. We usefdb_network_set_option()
for this matter.After setting everything we receive transaction timeouts and the following in client logs:
On the other hand setting environment variables
FDB_TLS_CERTIFICATE_FILE
,FDB_TLS_KEY_FILE
,FDB_TLS_CA_FILE
with the paths to the files with same content does the trick and everything works.We've also tried setting
FDBNetworkOption::FDB_NET_OPTION_TLS_KEY_PATH
and other_PATH
options with no effect as well.Environment:
Linux c31802bb42bc 6.5.0-17-generic #17-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 11 14:01:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: