Bug 888065
| Summary: | pidgin doesn't prompt for password after update to pidgin-sipe 1.14.0-1 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chad Feller <cfeller> |
| Component: | pidgin-sipe | Assignee: | Stefan Becker <chemobejk> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | chemobejk, ktdreyer |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-12-18 03:10:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chad Feller
2012-12-17 23:15:17 UTC
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. |