ASP.NET Core JWT Bearer: saita proxy na backchannel na metadata

Yi amfani da BackchannelHttpHandler kafin fara ɗebo, sai dai idan cikakken abokin ciniki ko mai sarrafa saiti na musamman ya riga ya mallaki wannan hanyar.

API na iya karɓar token na bearer sannan ya kasa wajen sauke metadata da maɓallin sa hannu na uwar garke. Saita wannan tsarin JWT bearer bayan rajistarsa da ke akwai kuma kafin buƙatun:

using System.Net;
using Microsoft.AspNetCore.Authentication.JwtBearer;

builder.Services.Configure<JwtBearerOptions>(
    JwtBearerDefaults.AuthenticationScheme, options =>
    {
        options.BackchannelHttpHandler = new HttpClientHandler
        {
            UseProxy = true,
            Proxy = new WebProxy("http://proxy.example:8080")
        };
    });

Daidaita sunan da aka yi rajista da shi; idan ya bambanta da Bearer na asali, yi amfani da ainihin sunansa. Ka kiyaye Authority, Audience da sigogin token da ke akwai. Ƙarshen metadata da maɓallin sa hannu na jama'a na iya amfani da ɗan takara daga jerin proxy na HTTP don wannan URL ɗin WebProxy mara asusu lokacin da aka ba da izinin shiga ta proxy na jama'a.

A daidaitaccen saiti, post-configuration na ƙirƙirar backchannel daga wannan handler. Idan cikakken Backchannel ko na musamman ConfigurationManager ya riga ya samar da mai ɗebo, sai ka saita wannan abu maimakonsa. Siffar handler ba ta wuce duka biyun ba.

Saita kowane asusun proxy a kan WebProxy kafin amfani, ba ta canza Proxy cikin SendAsync ba. Ka kiyaye issuer, audience, sa hannu, tsawon rai da ƙarin masu tabbatarwa. Shiga OIDC da samun token daban suna riƙe hanyoyin HTTP nasu.

Labarai masu alaƙa