Describe the bug
It's not possible with a specific account if you have multiple accounts already logged in your browser
Steps to reproduce
Simply have multiple Microsoft accounts and try to login with the Microsoft Login button and in your browser, you won't be greeted with a multiple account selection screen
Log output
not needed
Screenshots
not needed
Version
Downloader: latest
Hints at solving the issue
If we read the Micosoft doc, we can see that the prompt parameter can be added to the URL
prompt
optional
Indicates the type of user interaction that is required. Valid values are login, none, consent, and select_account. - prompt=login forces the user to enter their credentials on that request, negating single-sign on. - prompt=none is the opposite. It ensures that the user isn't presented with any interactive prompt. If the request can't be completed silently by using single-sign on, the Microsoft identity platform returns an interaction_required error. - prompt=consent triggers the OAuth consent dialog after the user signs in, asking the user to grant permissions to the app. - prompt=select_account interrupts single sign-on providing account selection experience listing all the accounts either in session or any remembered account or an option to choose to use a different account altogether.
One of the ways to solve this issue would be to simply always use the select_account prompt parameter
Another ways would be to add a setting or a launch arg to let the user setup an Interaction prompt if they wants
Describe the bug It's not possible with a specific account if you have multiple accounts already logged in your browser
Steps to reproduce Simply have multiple Microsoft accounts and try to login with the Microsoft Login button and in your browser, you won't be greeted with a multiple account selection screen
Log output not needed
Screenshots not needed
Version
Downloader: latest
Hints at solving the issue If we read the Micosoft doc, we can see that the prompt parameter can be added to the URL
Valid values are
login
,none
,consent
, andselect_account
.-
prompt=login
forces the user to enter their credentials on that request, negating single-sign on.-
prompt=none
is the opposite. It ensures that the user isn't presented with any interactive prompt. If the request can't be completed silently by using single-sign on, the Microsoft identity platform returns an interaction_required error.-
prompt=consent
triggers the OAuth consent dialog after the user signs in, asking the user to grant permissions to the app.-
prompt=select_account
interrupts single sign-on providing account selection experience listing all the accounts either in session or any remembered account or an option to choose to use a different account altogether.One of the ways to solve this issue would be to simply always use the select_account prompt parameter Another ways would be to add a setting or a launch arg to let the user setup an Interaction prompt if they wants