[
https://issues.apache.org/jira/browse/RATIS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910729#comment-16910729
]
Josh Elser commented on RATIS-636:
----------------------------------
{quote}Nit: For client configuration , to just differentiate , shouldn't it be
client-private-key.pem and client.crt (with common CA for mutual TLS)?
{quote}
Right you are! Thanks for catching :)
{quote}though I have not tested TLS locally with Ratis yet
{quote}
Yep, I need to walk through this locally, too.
> Add documentation for configuration TLS
> ---------------------------------------
>
> Key: RATIS-636
> URL: https://issues.apache.org/jira/browse/RATIS-636
> Project: Ratis
> Issue Type: Task
> Components: LogService
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Major
> Fix For: asf-site
>
> Attachments: RATIS-636.001.patch
>
>
> Ratis already has the ability to set up gRPC with TLS. Document this pieces
> of how this works, and how it might work for folks downstream.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
