Azure Key Vault .NET: saitin wakili don sirri da buƙatun tambari

Sanya irin wannan jigilar Azure Core ga SecretClientOptions da ClientSecretCredentialOptions kafin fara kowace hanya ta buƙata.

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

Yi amfani da ainihin vaultUrl, tenantId, clientId da clientSecret na aikace-aikacen. Sanya Transport = transport guda biyu da gangan ne: ɗaya yana jagorantar samun tambari ɗayan kuma buƙatun sirrin Key Vault.

Riƙe vaultUrl a matsayin ainihin ƙarshen ajiya. WebProxy na mai sarrafawa yana riƙe da mai shiga tsakani; akwai ƴan takarar HTTP na jama'a a cikin jerin wakilan HTTP lokacin da manufar cibiyar sadarwar ajiya ta yarda da wannan hanya; saita Credentials kafin gina abokan ciniki idan cibiyar sadarwa tana buƙata.

Sake amfani da jigilar don aikin abokan ciniki kuma saki albarkatun mallaka yayin kashewa. Haɗin wakili mai nasara yana kafa hanya, amma manufofin cibiyar sadarwa da samun damar Key Vault har yanzu suna yanke shawara ko aikace-aikacen na iya karanta sirrin.

Labarai masu alaƙa