-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Each client can be connected from mulitiple servers where each server ca... #104
Conversation
… can have its own CA.
In cases where each client can be connected from multiple servers and each server has its own CA keys and CA certs need to be separated |
Thanks for your work! Sorry, but I don't understand the benefit of your changes. What does this change allow you to do? |
Hi, Mark From: Raffael Schmid [notifications@github.com] Thanks for your work! Sorry, but I don't understand the benefit of your changes. What does this change allow you to do? — |
Okay, got it. You were talking about the client side, I somehow missed this when reading your explanation 😄 |
Each client can be connected from mulitiple servers where each server ca...
will this result in recreating all existing certificates on running servers ? that means we have to manually create the folder structure on running servers to prevent getting new certificates for all users ? |
Thanks for the merge. From: Raffael Schmid [notifications@github.com] Okay, got it. You were talking about the client side, I somehow missed this when reading your explanation [:smile:] — |
@peterbeck I don't think this will be a problem. The keys and certificates are just linked out of the Even though, the tarball will be recreated. |
Each client can be connected from multiple servers where each server can have its own CA