Re: mutual TLS peer_identity in arrow flight

Thank you folks, A PR says more than a thousand words :) https://github.com/apache/arrow/pull/8537 Certainly a much less ambitious change than propose in the auth redesign (which I am looking forward to btw). To James’ concern, the auth information is

Re: mutual TLS peer_identity in arrow flight

The authentication redesign goes further down the path of getting the peer identity from the authentication information. I would say that getting the peer context through mTLS is valid, but we shouldn't change the behavior of existing implementations of FlightProducers that get this from the auth h

Re: mutual TLS peer_identity in arrow flight

Hey Radu, That sounds fine to me, presumably if someone layers an authentication handler on top of mTLS, they don't want the mTLS identity anymore. Also note there's another auth redesign ongoing, though I don't think that conflicts with this, but maybe the authors there might think about how/if

mutual TLS peer_identity in arrow flight

Hi, I have a follow up question/feature proposal in the context of mutual TLS (introduced by https://issues.apache.org/jira/browse/ARROW-8742 ): In the context of mutual TLS the client is authenticated at TLS level and the client identity is avai