Azure Key Vault .NET: maxfiy ma'lumotlar va token so'rovlari uchun proksi sozlamalari

Ikkala so'rov yo'lidan birini boshlashdan oldin bir xil Azure Core transportini SecretClientOptions va ClientSecretCredentialOptions ga tayinlang.

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

Ilovaning haqiqiy vaultUrl, tenantId, clientId va clientSecret qiymatlaridan foydalaning. Ikki Transport = transport tayinlanishi ataylab: biri token olishni, ikkinchisi Key Vault maxfiy so'rovlarini yo'naltiradi.

vaultUrl ni omborning haqiqiy oxirgi nuqtasi sifatida saqlang. Ishlovchining WebProxy vositachini ushlab turadi; ombor tarmoq siyosati bu marshrutga ruxsat berganida HTTP proksi ro'yxatida ommaviy HTTP nomzodlari mavjud; tarmoq talab qilsa, mijozlarni yaratishdan oldin uning Credentials parametrini sozlang.

Transportni mijozlarning ish yuki uchun qayta ishlating va o'chirishda egalik qilingan resurslarni bo'shating. Muvaffaqiyatli proksi ulanish marshrut o'rnatadi, ammo ilova maxfiy ma'lumotni o'qiy olishini Key Vault tarmoq va kirish siyosatlari hal qiladi.

O'xshash maqolalar