-
Notifications
You must be signed in to change notification settings - Fork 61
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
Support mTLS on the Client Config for HTTPS #191
Comments
@skaravad Thanks for opening, I'll aim to add this weekend I'll add mTLS to the server too just for consistency, though will start with adding it to the agent |
Thank you @andydunstall , really appreciate it. |
hi @andydunstall , I was able to test the agent with mTLS , it is working as designed. Thank you so much for enabling this, it really helps to reinforce the security. Kudos to you and the contributors of this project , very simple, efficient and extensible, hope to see more features / adoption in the future. Thank you again for enabling this feature. |
We would like to offload TLS and mTLS (client cert auth) to a reverse proxy (HTTPS only) , so in theory Piko server need not have this feature.
On the Piko Client , if the TLS config can be extended to use client cert and key , it would really improve the overall security posture of the communication.
When mTLS is enabled , we can drop any un-authorized clients connections which is better security for servers open to the internet.
The text was updated successfully, but these errors were encountered: