Azure Key Vault .NET: dejinta proxy ee sirta iyo codsiyada token-ka

U xilsaar isla gaadiidka Azure Core ee SecretClientOptions iyo ClientSecretCredentialOptions ka hor inta aan la bilaabin mid kasta oo ka mid ah labada waddo ee codsiga.

var handler = new System.Net.Http.HttpClientHandler
{
    UseProxy = true,
    Proxy = new System.Net.WebProxy(
        "http://proxy.example.net:8080")
};

var transport = new Azure.Core.Pipeline.HttpClientTransport(handler);

var credential = new Azure.Identity.ClientSecretCredential(
    tenantId, clientId, clientSecret,
    new Azure.Identity.ClientSecretCredentialOptions
    {
        Transport = transport
    });

var vault = new Azure.Security.KeyVault.Secrets.SecretClient(
    new Uri(vaultUrl),
    credential,
    new Azure.Security.KeyVault.Secrets.SecretClientOptions
    {
        Transport = transport
    });

Isticmaal vaultUrl, tenantId, clientId iyo clientSecret dhabta ah ee abka. Labada xilsaar Transport = transport waa ula kac: mid wuxuu jiheeyaa helista token-ka kan kalena codsiyada sirta Key Vault.

Ku hay vaultUrl sidii barta dhabta ah ee dhammaadka kaydka. WebProxy ee maareeyaha wuxuu hayaa dhexdhexaadiyaha; musharrixiinta HTTP ee dadweynaha waxay laga heli karaa liiska proxy HTTP marka siyaasadda shabakadda kaydku u ogolaato waddadaas; habe Credentials ka hor inta aan macaamiisha la dhisin haddii shabakaddu u baahan tahay.

Dib u isticmaal gaadiidka shaqada macaamiisha oo sii daa kheyraadka la leeyahay marka la damiyo. Xiriir proxy ah oo guuleysta wuxuu sameeyaa waddo, laakiin siyaasadaha shabakadda iyo gelitaanka Key Vault ayaa weli go'aamiya haddii abku akhrin karo sirta.

Maqaallo la xiriira