Gyara hanyar wakili ta gefen uwar garke a cikin shiga OIDC na ASP.NET Core

Saita BackchannelHttpHandler a kan tsarin OpenID Connect da aka yi wa rijista don buƙatun ganowa da na token, sai idan manhajar ta samar da cikakken abokin ciniki na Backchannel.

Isar da burauza zuwa shafin shiga na mai ba da shaida ba ya tabbatar da cewa uwar garken ASP.NET Core za ta iya debo bayanan mai bayarwa ko musayar token. Waɗannan buƙatun na gefen uwar garke suna amfani da tashar baya ta OpenID Connect.

Ga wani tsari da ake da shi mai suna oidc, saita mai kula da shi yayin saitin ayyuka, kafin buƙatun tabbatarwa su fara:

services.Configure<Microsoft.AspNetCore.Authentication.OpenIdConnect
    .OpenIdConnectOptions>("oidc", options =>
{
    options.BackchannelHttpHandler =
        new System.Net.Http.HttpClientHandler
        {
            UseProxy = true,
            Proxy = new System.Net.WebProxy(
                "http://proxy.example.net:8080")
        };
});

Maye gurbin oidc da ainihin sunan tsarin da aka yi rijista. Riƙe saitunan authority, abokin ciniki da tabbatar da token. Idan wakilin yana buƙatar asusu, haɗa takardun shaidar da aka nufa zuwa WebProxy.

Duba ko manhajar tana riga ta samar da options.Backchannel a matsayin cikakken HttpClient. Idan tana yi, saita hanyar wancan abokin ciniki kai tsaye: ASP.NET Core na amfani da BackchannelHttpHandler lokacin ƙirƙirar tashar bayansa ta asali, ba don maye gurbin abokin ciniki da aka riga aka samar ba.

Yi amfani da gazawar buƙatar ganowa ko ta token daga uwar garke don kimanta wannan saitin. Ga hanyar HTTP ta jama'a, jerin wakilan HTTP yana ba da 'yan takara don adireshin WebProxy. Manufar wakili ta burauza da abokan cinikin HTTP marasa alaƙa suna da hanyoyin saiti nasu.

Labarai masu alaƙa