Replies: 4 comments
-
@lely475 thanks for your interest and question! This is a very good question. @yhwen @nvidianz @IsaacYangSLA do you know how can we configure our "project.yml" in this case? |
Beta Was this translation helpful? Give feedback.
-
NVFlare requires the direct client certificate for authentication. The proxy needs to be configured as to pass through the client certificate to the server.
|
Beta Was this translation helpful? Give feedback.
-
@lely475 I know some teams successfully do this multi-hopping of network. Can you try the 2.3 version of NVFlare? The client certificates should put on client side and server certificates on server side same as a regular setup. Your proxy needs to be a "pass through" as @yhwen suggested |
Beta Was this translation helpful? Give feedback.
-
Hi @YuanTingHsieh, I just realized I never closed this discussion. Yes, we are now using the 2.3 version of NVFlare. In the end it turned out not to be a proxy problem, but an incorrect whitelist on server side. |
Beta Was this translation helpful? Give feedback.
-
Dear NVFlare community,
I am trying to establish connection between a provisioned NVFlare server and client.
The client is only able to communicate to the server through a HTTPS proxy that is handling all incoming and outgoing HTTPS traffic.
I am currently unable to establish the connection, where I get the following error from the server:
And on client side:
Is it possible that I need to place the client SSL certificate, private key and root certificate on the proxy, to enable a successful TLS handshake? Or should this not be a problem and the issue lies elsewhere?
Thank you already.
Beta Was this translation helpful? Give feedback.
All reactions