Gets the token through an interactive process that prompts the user for credentials through a browser like in @azure/ms-rest-nodeauth library.
It is necessary for authenticating user/password with configured 2FA in the Azure portal.
Notice that node.js doesn't support opening browser window, so library needs to return the url where user can pass the credentials (like in @azure/ms-rest-nodeauth).
Tagging for review to see if this is something that could be in the common libraries for the SDKs.
In my opinion that should be implemented as soon as possible. Your team says that @azure/ms-rest-nodeauth will be deprecated soon and @azure/identity doesn't support all functionalities.
Interactive authentication is the only one method, which you can authenticate AAD user with 2FA configured.
Hi Kacper, let me clarify what I was telling the PR author in https://github.com/Azure/ms-rest-nodeauth/pull/75#issuecomment-519198541: we aren't deprecating ms-rest-nodeauth anytime soon, I was merely letting the author know that we are focusing our attention on @azure/identity at the moment.
Regardless of what I said there, we are taking steps to ensure that ms-rest-nodeauth remains compatible with the new SDK libraries for the forseeable future. You shouldn't worry about ms-rest-nodeauth going away before @azure/identity has the appropriate credential coverage.
Let me know if I can provide any further clarification!
That's clear now. Thank you @daviwil.
I wanted that information to know, how should I have to plan my work. I'm working on a project which needs Interactive Authentication support and now I know what is going on.
I'm waiting for any updates 👀
@funkydev - We've added a few additional ways to authenticate to the Identity library.
One possible fit for what you're looking for is device code credential, which let's you interactively get a code on your device that you can use to log in with. Is this similar to what you're looking for, by chance?
@jonathandturner Right, Device Code Credentials are what I've looked for. It solves the issue, thank you! ✋
We are still planning to implement InteractiveBrowserCredential for Node.js but didn't have time to include it in the 1.0 GA release. We hope to get it implemented in a future feature update in early 2020.
Closing as this is now available as part of https://www.npmjs.com/package/@azure/identity/v/1.2.0-beta.1. You can use the InteractiveBrowserCredential in node, and doing so will pop up the user's default web browser, start a web server, and redirect the token from the browser back to your application.
Please let us know how this works for you.
Most helpful comment
Hi Kacper, let me clarify what I was telling the PR author in https://github.com/Azure/ms-rest-nodeauth/pull/75#issuecomment-519198541: we aren't deprecating
ms-rest-nodeauthanytime soon, I was merely letting the author know that we are focusing our attention on@azure/identityat the moment.Regardless of what I said there, we are taking steps to ensure that
ms-rest-nodeauthremains compatible with the new SDK libraries for the forseeable future. You shouldn't worry aboutms-rest-nodeauthgoing away before@azure/identityhas the appropriate credential coverage.Let me know if I can provide any further clarification!