Bug 466510
| Summary: | bodhi-client exits silently on wrong password | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ville Skyttä <ville.skytta> |
| Component: | bodhi | Assignee: | Luke Macken <lmacken> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | a.badger, lmacken, pfrields, tim.lauridsen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-07-08 02:23:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ville Skyttä
2008-10-10 16:57:46 UTC
It just happened to me again, twice, and it's pretty infuriating to refill the bodhi template several times. Any thoughts when this might be fixed? I took a look at this and think I've found the problem. Basically, bodhi-client and bodhi-server work around a problem in python-fedora-0.2.x with an incomplete hack on the client side. python-fedora-0.2.x didn't correctly handle a response code of 403 so bodhi-server disables returning of that value when authentication is requested. python-fedora-0.3.x remedies that and depends on the 403 response code to know that it needs to raise an AuthError. So bodhi-server should now uncomment this line in controllers.py::login(): # cherrypy.response.status=403 Note that bodhi-client has been working around this problem by looking for a specific message being returned from the login() method:: if 'message' in data and data['message'] == u'You must provide your credentials before accessing this resource.': This bug was occurring because a wrong password returns a different message. As long as returning 403 works, we should abandon use of this workaround. Luke says he'll push an updated bodhi server tomorrow with the 403 uncommented so bad passwords should start re-prompting then. Sorry for the delay -- had to get some +1's to perform the bodhi upgrade during the pre-release freeze. I applied the patch to our production instance, but the client will still need to be fixed. I'll see if I can push out a new client shortly. Ville, could you test this with the latest bodhi client now that the server changes have been made? I have bodhi-client-0.5.3-1.fc9.noarch and python-fedora-0.3.7-1.fc9.noarch and it seems to work. I didn't submit an update, though, just verified that typing in an incorrect password re-prompts me. Yep, re-prompts also with bodhi-client-0.5.3-1.fc9.noarch and python-fedora-0.3.6-2.fc9.noarch, thanks. Would not hurt to add a "Invalid username or password" error message before the re-prompt though, but this is already a very good improvement. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This issue has been resolved and verified. |