我们现在使用SemaphoreSlim来控制对试图获取令牌的代码的访问。
在这个问题的评论线程中进行了一些讨论之后，我确实考虑过使用lock语句，但在 Package 异步调用时，这并不被认为是一个好主意，这是因为潜在的死锁和不同线程在等待返回时试图释放它们没有访问权限的锁的可能性。
代码现在如下所示

await this.semaphoreSlim.WaitAsync();

try
{
    var account = await this.GetCurrentAccount();
    AuthenticationResult result = await this.pca.AcquireTokenSilent(scopes, account).ExecuteAsync();
    return new AuthenticationResultWrapper(result);
}
catch (MsalUiRequiredException)
{
    try
    {
        // Acquire token interactively
        AuthenticationResult authResult = await this.pca.AcquireTokenInteractive(scopes)
                                                        .WithParentActivityOrWindow(this.uiParent)
                                                        .ExecuteAsync();

        return new AuthenticationResultWrapper(authResult);
    }
    catch (MsalServiceException client) when (client.Message.Contains(BreathRmCloudDataSyncService.MsalForgottenPasswordErrorMessageCode))
    {
        // User selected forgotten password flow
        IAuthenticationResult authResult = await this.HandleClinicalServiceHandleForgottenPasswordAsync();
        return authResult;
    }
    catch (MsalException msalException) when (BreathRmCloudDataSyncService.ExceptionIsMsalCancellation(msalException))
    {
        // Nothing to do here, user cancelled the flow
        this.logger.LogInteraction("User cancelled authentication during interactive token acquirement.");
        throw;
    }
    catch (Exception exc)
    {
        this.logger.LogException(exc, "AcquireTokenInternalAsync Try Interactively Failed: Unknown Exception: " + exc.Message);
        return null;
    }
}
catch (Exception e)
{
    this.logger.LogException(e, "ClinicalService - AcquireTokenAsync");
    throw;
}
finally
{
    this.semaphoreSlim.Release();
}