microsoft-authentication-library-for-dotnet VS microsoft-identity-web

In your console app code when you initialize the MSAL client app ( IConfidentialClientApplication ) one of its properties is the token cache (AppTokenCache and UserTokenCache) which handles all the token management stuff like using the refresh token for you when you call the AcquireTokenForClient method. Read more here

# Title URL Accessed-On 1 Desktop app that calls web APIs: Acquire a token using WAM https://learn.microsoft.com/en-us/azure/active-directory/develop/scenario-desktop-acquire-token-wam 2023-01-11 2 Azure SDK Releases https://azure.github.io/azure-sdk/releases/latest/all/python.html 2023-01-11 3 azure-identity 1.13.0b1 https://pypi.org/project/azure-identity/1.13.0b1/ 2023-01-11 4 WAM https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/wam 2023-01-11 5 class InteractiveBrowserCredential(InteractiveCredential) https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/identity/azure-identity/azure/identity/_credentials/browser.py 2023-01-11 6 Add WAM Support to MSAL for Python, for cross-language consistency #451 https://github.com/AzureAD/microsoft-authentication-library-for-python/issues/451 2023-01-11

For end to end testing, you can setup test accounts, test applications or even separate directories. Username and passwords can be deployed via the Continuous Integration pipeline (e.g. secret build variables in Azure DevOps). Another strategy is to keep test credentials in KeyVault and configure the machine that runs the tests to access KeyVault, for example by installing a certificate. Feel free to use MSAL's strategy for accessing KeyVault. See more info about Testing an app using MSAL here and video about UI testing Azure AD protected single page applications with Cypress.

MauiApps is where you'll find the app in this rather large repository.

Given https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/3033

Fore query "cannot persist Microsoft authentication token cache securely!" (with quotes) Google returns single result, written in Chinese. Luckily I opened that Chinese result and spotted link to that issue.

duck.com does find the issue at hand.

I mean GitHub is no small site, but somehow I expected that Google will find my ANY public string on the internet.

ADAL is the older package now, and MSAL.NET is the latest library they're pushing for publish (Azure.Identity is still being worked on and is pushed for internal SDK usage from what I can tell, but this is what I primarily use due to easy code).

I'm using MSAL.NET and the library API automatically refreshes the token, if needed, when the token is silently acquired.

The article "MSAL.NET or Microsoft.Identity.Web" might be helpful: https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/MSAL.NET-or-Microsoft.Identity.Web

Are you using MSAL.NET? I've recently done this for a proof-of-concept app in Forms... Look at this sample.

have you looked into using MSAL 2.0? This would be a good start

Microsoft.Identity.Web's source code.

I'm working on migrating a single-tenant, single-db ASP.NET Core Web API project that uses Azure AD with a DistributedSqlServerCache to support a multi-tenant, multi-db approach.

Last week I was asked by someone in the community for a sample that shows how to secure Azure Functions with Azure AD. And specifically, a .NET 5 or 6 Azure Function using the Microsoft.Identity.Web library to validate tokens and authorize access.

Also, check out Microsoft.Identity.Web https://github.com/AzureAD/microsoft-identity-web. It’s another wrapper around MSAL. It wraps some common best practices a little better than Azure.Identity does.

In a previous blog post, we looked at how to migrate the authentication code of a front-end solution written with ASP.NET Core to using the latest Microsoft.Identity.Web library for .NET. That was part 1 of our short series. For part 2, we will look at how to modernize the auth code in our back-end API using Microsoft.Identity.Web again.

You should check this out: https://github.com/AzureAD/microsoft-identity-web/wiki/customization

About 3 years ago, I wrote some code for a customer. It was as sample solution. The front end was as straight up ASP.NET Core MVC app. The backend API was a simple .NET Core API. Both made use ofOpen ID Connect (OIDC) and OAuth2 to authenticate users and acquire tokens in order to retrieve and update a ToDo list. The juice of the app is in the authentication. So in this blog post, we'll look how to take out the "old" authentication code and replace it with the latest and greatest in ASP.NET Core - Microsoft.Identity.Web. The blog will come in two parts: