ASP.NET Core JWT Bearer: setha i-proxy ye-backchannel yemethadata

Sebenzisa i-BackchannelHttpHandler ngaphambi kokuthi ukulanda kuqale, ngaphandle uma iklayenti eliphelele noma umphathi wokuhlela oqondisiwe esenayo leyo ndlela yokuhamba.

I-API ingamukela i-bearer token bese yehluleka ekulandeni imethadata nokhiye wokusayina wesiphakamiso. Hlela lowo mkhuba we-JWT bearer ngemva kokubhaliswa okukhona nangaphambi kwezicelo:

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")
        };
    });

Qhathanisa negama elibhalisiwe; uma lehlukile ku-Bearer okuzenzakalelayo, sebenzisa igama langempela. Gcina i-Authority, i-Audience namapharamitha we-token akhona. Iphetho lomethadata nokhiye wokusayina womphakathi lingasebenzisa umgqatjwa ovela ohlaweni lwama-proxy e-HTTP lwale URL ye-WebProxy engena-akhawunti uma ukufinyelela nge-proxy yomphakathi kuvunyelwe.

Kusethaphu ejwayelekile, i-post-configuration yakha i-backchannel kusuka kulesi siphathi. Uma i-Backchannel ephelele noma i-ConfigurationManager yangokwezifiso isivele inikeza isitholi, hlela leyo nto esikhundleni salokho. Isakhiwo sesiphathi asikushintshi kokubili.

Setha noma iyiphi i-akhawunti ye-proxy ku-WebProxy ngaphambi kokusetshenziswa, hhayi ngokushintsha i-Proxy ngaphakathi kwe-SendAsync. Gcina i-issuer, i-audience, isiginesha, isikhathi sokuphila nezinye iziqinisekisi. Ukungena nge-OIDC nokutholwa kwe-token okuhlukile kugcina izindlela zazo ze-HTTP.

Izihloko ezihlobene