Separation of code generation & verification

[TheVeryStarlk]

Summary

Currently, the way code flow authentication works is by calling AcquireTokenWithDeviceCode and using the callback it provides, that callback gets called inside ExecuteAsync, which also waits for the token response.

Motivation and goals

1-2 paragraphs, or a bullet-pointed list. What existing pain points does this solve? What evidence shows it's valuable to solve this?

In scope

Possibly a new method in IPublicClientApplication.

Out of scope

None that I am aware of.

Risks / unknowns

None that I am aware of.

Examples

string code = await _application
    .AcquireDeviceCodeAsync();

AuthenticationResult? result = await _application
    .AcquireTokenWithDeviceCode(_scopes, code)
    .ExecuteAsync();