Description of problem: After update to pidgin-sipe/purple-sipe 1.14.0-1, pidgin no longer prompts me for my Communicator password. Instead it just fails with "Password required'. Pidgin debug window shows the following: (15:06:17) account: Connecting to account foo,foo. (15:06:17) connection: Connecting. gc = 0x1367710 (15:06:17) connection: Connection error on 0x1367710 (reason: 2 description: Password required) Version-Release number of selected component (if applicable): pidgin-sipe-1.14.0-1.fc18.x86_64 purple-sipe-1.14.0-1.fc18.x86_64 pidgin-2.10.6-4.fc18.x86_64 How reproducible: always Steps to Reproduce: 1. Have a communicator profile w/out a saved password 2. try to sign in 3. Actual results: sign in fails, without prompting for password Expected results: pidgin should prompt for password Additional info: Previous version(s) of pidgin-sipe/purple-sipe would prompt for password. 1.13.3-1 had no such issue.
This is an intentional change, because Kerberos Single Sign-On users don't want to enter a password. As Pidgin does not know how to handle protocol plugins that can have password and password-less modes I opted for a compromise: if a password is required then the account setup will fail immediately with the error message "Password required". You'll have to save a password with the account. Closing as NOTABUG.
This is problematic as Pidgin saves the password in plaintext in ~/.purple/accounts.xml. There is a "Use Single Sign-On" setting checkbox under the advanced tab. Is there a way to make it check that setting first, and only not prompt for a password if that checkbox is set?
No, there is no such way, because Pidgin opens the password request based on the compiled-in hard-coded "password is optional" plugin flag not being set *BEFORE* calling the account. The previous solution annoyed Single Sign-On users and several times they simply submitted a git commit to set that flag in the plugin code, which I had then to revert. This compromise is currently the best solution. I just checked the API documentation and there might be a possible work around.
If you are interested, please check out the alternative implementation for Pidgin password-less support from git commit a1fd830. This will be included in the next release.
pidgin-sipe-1.14.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/pidgin-sipe-1.14.1-1.fc18
pidgin-sipe-1.14.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/pidgin-sipe-1.14.1-1.fc17
pidgin-sipe-1.14.1-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/pidgin-sipe-1.14.1-1.fc16
pidgin-sipe-1.14.1-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
pidgin-sipe-1.14.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
pidgin-sipe-1.14.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.