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
I think there is a security requirement that client private key can be encrypted if I use the SSL authentication to connect Nebula by nebula-java.
Now I just can define the path for the certs like crtFilePath, keyFilePath, caCrtFilePath. But somehow I need to encrypt the cert file. However the CASignedSSLParam doesn't contain the parameter "password".
I suggest this parameter should be added in CASignedSSLParam and I can pass it in nebula-java.
The text was updated successfully, but these errors were encountered:
I have noticed that the issue you created hasn’t been updated for nearly a month, so I have to close it for now. If you have any new updates, you are welcome to reopen this issue anytime.
I think there is a security requirement that client private key can be encrypted if I use the SSL authentication to connect Nebula by nebula-java.
Now I just can define the path for the certs like crtFilePath, keyFilePath, caCrtFilePath. But somehow I need to encrypt the cert file. However the CASignedSSLParam doesn't contain the parameter "password".
I suggest this parameter should be added in CASignedSSLParam and I can pass it in nebula-java.
The text was updated successfully, but these errors were encountered: