Kiran Graph API da buƙatun token na ClientSecretCredential suna da wuraren shiga dabam. Tare da Microsoft.Graph 5 da Azure Identity, saita duka biyu kafin gina abokin ciniki:

var proxy = new System.Net.WebProxy(
    "http://proxy.example.net:8080");

var tokenHandler = new System.Net.Http.HttpClientHandler
{
    Proxy = proxy,
    UseProxy = true
};

var credentialOptions = new Azure.Identity.ClientSecretCredentialOptions
{
    Transport = new Azure.Core.Pipeline.HttpClientTransport(tokenHandler)
};

var credential = new Azure.Identity.ClientSecretCredential(
    tenantId, clientId, clientSecret, credentialOptions);

var authProvider =
    new Microsoft.Kiota.Authentication.Azure.AzureIdentityAuthenticationProvider(
        credential, scopes: new[] { "https://graph.microsoft.com/.default" });

var graphHttp = Microsoft.Graph.GraphClientFactory.Create(proxy: proxy);
var graphClient = new Microsoft.Graph.GraphServiceClient(
    graphHttp, authProvider);

Don hanyar HTTP ta jama'a marar tabbaci, jerin proxy na HTTP yana ba da adireshi masu yiwuwa don WebProxy da aka raba. Aikace-aikacen yana ba da tenantId, clientId da clientSecret ta hanyar sarrafa takardun shaidar da yake da su. Ƙarfin .default yana amfani da izinin aikace-aikacen da aka saita don wannan rajista; hanya ba za ta iya ba da izini ba.

Karanta layukan sufuri biyu a matsayin ma'auratan da suka fi muhimmanci. HttpClientTransport(tokenHandler) yana ɗaukar buƙatar token na takardar shaidar. GraphClientFactory.Create(proxy: proxy) yana kiyaye ginin middleware na HTTP na Graph SDK yayin da yake saita hanyar API ɗinsa.

Idan mai shiga tsakani yana buƙatar tabbaci, sanya asusun da ake buƙata a kan Credentials na abin proxy. Riƙe sufuri mallakar ku tsawon rayuwar ɓangaren kuma ku sake su yayin kashewa.

Yi amfani da wannan tsarin tare da ƙarni na SDK da aka ambata. Misalan HttpProvider da DelegateAuthenticationProvider na ƙarni na baya ne kuma ba za a iya haɗa su cikin wannan sarkar ginin ba.

Labarai masu alaƙa