Allow to specify scope when using device code authentication

This issue is a follow up from Azure/azure-sdk-for-node#5190 which was logged for the ms-rest-azure package which in turn uses the adal-node package for all the auth work

The above linked issue uses https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-device-code#protocol-diagram as a reference and expects the ability of passing the scope when making the request to the /devicecode endpoint.

When I looked into the adal-node package, I see the scope being set to openid at

azure-activedirectory-library-for-nodejs/lib/token-request.js

Line 207 in 023fb2e

oauthParameters[OAuth2Parameters.SCOPE] = OAuth2Scope.OPENID;

, and that too only when the grant type is not device code, client credentials and auth code

Can someone provide some clarification on what one should do when they need to set the scope?

cc @jefjos who logged the original issue and should be able to answer any follow up question on the issue

@ramya-rao-a Is this still an issue with msal-node?

Since ADAL is reaching end of life, as mentioned in the guidance, we would like to address any applicable issues on msal-node. Please give it a spin and let us know. If you are still facing an issue, please feel free to open an issues against the new. repo.