WAM does not integrate with browser's password manager

[elygre]

az login says that you are preparing to switch to WAM (Web Authentication Manager). The message says "To help us collect feedback on the new login experience, you may opt-in to use WAM by running the following commands", which indicates that you want feedback. At the same time, you don't say where, so I chose this channel.

My feedback: WAM does not seem to integrate with my password manager. This creates a much more annoying workflow: The WAM-window opens, i select the username, I have to switch to a browser, open the password manager, copy the password, return to the WAM-window, paste the password, submit the login, switch to my command line.

The corresponding browser-login is much simpler: The browser opens, I select the username, password is automatically filled, I submit, and switch to the command line.

So, for me, the important command is az config set core.allow_broker=false, which I hope will remain operational.

[yonzhan]

@jiasli for awareness

[rayluo]

WAM does not seem to integrate with my password manager. This creates a much more annoying workflow: The WAM-window opens, i select the username, I have to switch to a browser, open the password manager, copy the password, return to the WAM-window, paste the password, submit the login, switch to my command line.

Hi @elygre , did you need to do that just once, or did you need to do that for every "az login" even for the same account?

[elygre]

So there are two levels of "az login".

• First, when Azure requires a login, because for example "Your organizational policy requires you to sign in again after a certain time period." In these scenarios I need to enter a password, and the WAM password dialog does not integrate with my password manager -- and probably not with any password manager?
• Second, if I for example open a new shell and execute a new "az login" before the login expiration, then a new login is not required, and a new password is not required, and therefore the password manager integration is not required.

For my organization, the login lifetime is measured in a few hours, and I need multiple "real" logins during a workday.

[ms6073]

Wanted to comment that on my Win 10 laptop, running the suggested commands resulted in my no longer being able to to actually login to the azure client!

az config set core.allow_broker=false
az account clear
az login

After which login attempts returned a variety of errors, the most common that was repeated with each logon attempt was as follows. Fortunately I stumbled across the OP and was able to resolve the issue setting core.allow_broker=true:

Winrt exception was thrown during GetTokenSilently '(pii)'.. Status: Response_Status.Status_Unexpected, Error code: -2147023584, Tag: 590996738
Please explicitly log in with: az login

[rayluo]

Wanted to comment that on my Win 10 laptop, running the suggested commands resulted in my no longer being able to to actually login to the azure client!

az config set core.allow_broker=false az account clear az login

After which login attempts returned a variety of errors, the most common that was repeated with each logon attempt was as follows. Fortunately I stumbled across the OP and was able to resolve the issue setting core.allow_broker=true:

Winrt exception was thrown during GetTokenSilently '(pii)'.. Status: Response_Status.Status_Unexpected, Error code: -2147023584, Tag: 590996738 Please explicitly log in with: az login

Are you sure you did not actually use the "...allow_broker=true" or "...false" in the opposite way? That error message would only show up when broker was in effect.