ThreeMammals/Ocelot

Support for Client certificates for downstream routes

Open

#1,690 opened on 2023年9月12日

GitHub で見る
 (10 comments) (0 reactions) (1 assignee)C# (8,137 stars) (1,617 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.