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.