Takardun shaidar wakili a tsalle na biyu na PowerShell

Buƙatar yanar gizo da ke aiki kai tsaye a uwar garke B na iya samun 407 idan an gudanar da wannan umarni a can ta hanyar PowerShell remoting. Shiga daga A zuwa B ba ya ba da wannan ainihi kai tsaye don musayar tabbaci na gaba a B.

A → remoting session on B → HTTP proxy → website

Ɗaya daga cikin ƙirar da aka amince da ita ita ce ba da asusun wakili a fili don buƙatar fita. Tare da PSSession data kasance da wani abu na PSCredential da aka samu yadda ya kamata:

Invoke-Command -Session $session -ArgumentList $proxyCredential -ScriptBlock {
    param([pscredential]$outboundProxyCredential)

    $requestOptions = @{
        Uri = 'https://api.example/'
        Proxy = 'http://proxy.example:8080'
        ProxyCredential = $outboundProxyCredential
    }
    Invoke-WebRequest @requestOptions
}

Abun shaidar yana don asusun wakili da aka nufa. Zaman yana ci gaba da amfani da tabbacin remoting na yau da kullum, kuma duk wani shiga gidan yanar gizo ya kasance wani ɓangare na buƙatar wannan gidan.

Wannan yana guje wa dogaro da ba da izini kai tsaye na shiga na farko. Amma yana buƙatar uwar garken nesa ta kula da kayan asusun da aka bayar a matsayin ɓangare na tsarin gudanarwa da aka nufa. Wasu gine-gine, kamar tashar RunAs da aka sarrafa ko iyakantaccen damar sabis, suna da nasu bukatun daidaitawa.

Idan takardun shaidar wakili na asali sune kuskuren zato, rubuta asusun da umarnin nesa ke gudana a ƙarƙashinsa da tabbacin da wakilin ke buƙata. Tsawaita lokacin buƙatar yanar gizo ba zai iya ba da shaidar da ta ɓace ba.

Zaɓuɓɓukan wakili akan New-PSSessionOption sun shafi haɗin remoting kanta. Saita Invoke-WebRequest a cikin rukunin rubutun nesa lokacin da haɗin yanar gizo na waje na B shine ke buƙatar wakilin.