If you enable single signon thru the preference pane, it becomes functional without entering a password. On future sessions, it prefills username/passwords without asking for a password. I assume this is because html dialogues have not been tied in yet? If I set use.walletDialogs to true then the console is used for authentication.

This is the correct behavior. In order to be asked for a password (or to be asked anything for that matter), you need to have the preference wallet.useDialogs (not use.walletDialogs as mentioned in this report) to true before you enter the browser. This preference is not setable from the preference panel because it is a temporary preference that can be used to simulate dialogs at this time; it will no longer be needed when true dialogs are available. BTW, when the wallet.useDialogs preference is not true, a default password is used -- that password is the single character '~'.

The point of this bug was basically to use as a placeholder until true dialogues are hooked up. Does that not seem reasonable? - I assume passwords will 'automatically' be asked for once they are hooked up, right? I don't have a problem with no password being required right now.

If that's the purpose, then lets do it cleanly. Open another bug report stating that dialogs are not being used in wallet and single signon unless a secret pref is set. You can assign that one to me.

6607 filed