Describe the bug
I have an android-app, works with device-authentication-flow (and browser-authentication-flow). No issues, after the user logs in, I receive a token and can access my backend.
Once the user clicks log-in-via-device, I call acquireTokenWithDeviceCode. My app then shows a QR code, with the url and device-code.
MSAL starts "pinging" some backend to receive confirmation that the user has logged in. And this "pinging" continues until the user does.
However the user could choose not to log in at all (in my app, he can press back).
How do I tell MSAL to cancel the device-authentication-flow, I don't want it to keep "pinging" the backend for confirmation that the user has logged in on another device.
Expected behavior
There should be some interface to cancel the acquireTokenWithDeviceCode call. (It seems to be present on dotnet with a CancellationToken)
Actual Behavior
There is no way to stop the acquireTokenWithDeviceCode-flow other than waiting for the timeout to happen.
hi @DumTiDum, Based on my discussion with the eng team, this is an expected behavior. We took a note of your suggested enhancement and will evaluate on our side. Thanks.
Describe the bug I have an android-app, works with device-authentication-flow (and browser-authentication-flow). No issues, after the user logs in, I receive a token and can access my backend.
Once the user clicks log-in-via-device, I call acquireTokenWithDeviceCode. My app then shows a QR code, with the url and device-code. MSAL starts "pinging" some backend to receive confirmation that the user has logged in. And this "pinging" continues until the user does.
However the user could choose not to log in at all (in my app, he can press back).
How do I tell MSAL to cancel the device-authentication-flow, I don't want it to keep "pinging" the backend for confirmation that the user has logged in on another device.
Expected behavior There should be some interface to cancel the acquireTokenWithDeviceCode call. (It seems to be present on dotnet with a CancellationToken)
Actual Behavior There is no way to stop the acquireTokenWithDeviceCode-flow other than waiting for the timeout to happen.