Univention Bugzilla – Bug 33503
401 status error is not correctly interpreted to open the login dialogue
Last modified: 2013-11-28 16:00:51 CET
+++ This bug was initially created as a clone of Bug #33443 +++ Currently, the updater module does not handle 401 (=unauthorized) errors correctly, therefore the login dialogue is not opened if the UMC server is restarted in the update process. The problem is in the method umc/modules/updater:handleQueryError(). The handling is not correct: > handleQueryError: function(subject, data) { > ... > if (data.status == 401) { ... } > ... > } At this point "data" has the following structure: > { > "stack": "...", > "message": "Unable to load /umcp/command/updater/installer/status status: 401", > "response": { > "url": "/umcp/command/updater/installer/status", > "options": { > "method": "POST", > "data": "{\"options\":{\"job\":\"distupgrade\"}}", > "handleAs": "json", > "headers": { > "Content-Type": "application/json" > } > }, > "xhr": { > "statusText": "Unauthorized", > "status": 401, > "response": "{\"status\": 401, \"message\": \"None\"}", > "responseType": "", > "responseXML": null, > "responseText": "{\"status\": 401, \"message\": \"None\"}", > "upload": { > "onprogress": null, > "onloadstart": null, > "onloadend": null, > "onload": null, > "onerror": null, > "onabort": null > }, > "withCredentials": false, > "readyState": 4, > "timeout": 0, > "onreadystatechange": null, > "ontimeout": null, > "onprogress": null, > "onloadstart": null, > "onloadend": null, > "onload": null, > "onerror": null, > "onabort": null > }, > "loaded": 34, > "total": 34, > "status": 401, > "text": "{\"status\": 401, \"message\": \"None\"}", > "data": { > "status": 401, > "message": "None" > } > } > } Correct would be data.response.status == 401. However, even more correct would be to use the UMC wide error handling.
Fixed in univention-updater 8.0.78-8.1237.201311211757 YAML updated, no changelog required (3.2-0 already released)
OK: source code change 3.1-1 OK: functionality 3.1-1 After the update to UCS 3.2 a login dialog is shown below a UMC refresh (F5) question. The login dialog contained no login buttons (due to the changed hash) but a login is possible if Enter is pressed. Prior to that the user must have denied the UMC refresh, otherwise the login dialog is unreachable. OK: package build/package version OK: YAML
http://errata.univention.de/ucs/3.1/196.html