ThreeMammals/Ocelot

Support for Client certificates for downstream routes

Open

#1,690 创建于 2023年9月12日

在 GitHub 查看
 (10 评论) (0 反应) (1 负责人)C# (8,137 star) (1,617 fork)batch import
MVPfeaturehelp wantedlarge effortmedium effort

描述

New Feature

Extend the definition of downstream routs to support specifying a client certificate that is the used to call the service.

Motivation for New Feature

We are looking at using Ocelot as the API gateway for a new project. The problem is that the downstream services require that the usage of client certificates to authenticate (they contain PII). This feature would enable this setup.

贡献者指南

技术栈
csharp
领域
backendapiauthentication
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
C#.NETASP.NET CoreOcelot basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
The issue requests adding client certificate support to downstream route configuration. To implement, look at how existing downstream route options are defined (e.g., in Ocelot's configuration model and HTTP client factory). The authentication handler for client certificates likely needs to be integrated in the HttpClient creation pipeline. Refer to the existing code in `Ocelot.Requester` and `Ocelot.HttpClient` namespaces. The assigned developer has not provided any PR yet, so consider checking if there is a pending design discussion in the comments.