Acquire a token when PlatformParameters definition change migrating to .NET Core 3.1

[isthisworking]

Hi All,
 
I've run into a problem with a C# console app that (for reasons) is being moved from .NET Framework to .NET Core. In the process of retargeting the app, the following line of code to get the access token is no longer syntactically correct:
 
AuthenticationResult result =
    await m_authenticationContext.AcquireTokenAsync(
        resourceUri,
        clientID,
        new Uri(redirectUri),
        new PlatformParameters(PromptBehavior.Auto));
 
The constructor for PlatformParameters no longer accepts the single parameter. It now requires a second parameter of ICustomWebUi. The desired (and previous) behavior of the console app is that, when run, it does not require user interaction to authenticate. This needs to run headless. What would be the easiest method to refactor the code to maintain parity?
 
Thanks.

[michaelx2]

Hello @isthisworking ,

The seconed parameter ICustomWebUi is extension method enabling ADAK.NET extenders for public client applications to set a custom web ui that will let the user sign-in with Azure AD, present consent if needed, and get back the authorization code.  You may refer to a sample implement here:

https://github.com/AzureAD/azure-activedirectory-library-for-dotnet/blob/66f89589b878c1a7cfb12e46f60... 

In your scenario, you want to run the app in headless mode, since that, you may try to use 3rd party library PowerBI.Api.Client  which already implemented Automatic OAuth2 authentication.

Best Regards