Bug 36636
| Summary: | Endless UMC login animation after AUTH login error [401] | ||
|---|---|---|---|
| Product: | UCS | Reporter: | Alexander Kläser <klaeser> |
| Component: | UMC (Generic) | Assignee: | Florian Best <best> |
| Status: | CLOSED FIXED | QA Contact: | Alexander Kramer <kramer> |
| Severity: | normal | ||
| Priority: | P5 | CC: | best, gohmann, walkenhorst |
| Version: | UCS 4.0 | Flags: | best:
Patch_Available+
|
| Target Milestone: | UCS 4.0-0-errata | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=36400 | ||
| What kind of report is it?: | --- | What type of bug is this?: | --- |
| Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
| User Pain: | Enterprise Customer affected?: | ||
| School Customer affected?: | ISV affected?: | ||
| Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
| Ticket number: | Bug group (optional): | Error handling, Usability | |
| Max CVSS v3 score: | |||
| Attachments: | patch | ||
(In reply to Alexander Kläser from comment #0) > An error message should be shown instead. > Maybe we could also add a hint that the server process is not running? → I created somewhere a bug for this, the error status in that case is wrong. It should not be 401 but 503 Service Unavailable. Created attachment 6363 [details]
patch
The "display: block" attribute wasn't set. Does not happen always. Maybe only when there was a message already shown. Can be easy reproduced if the umc-server is not running.
Patch applied in svn r57683. The message that the UMC-server is not running was done at Bug #36400. Package: univention-management-console-frontend Version: 4.1.106-11.993.201501301040 YAML: 2015-01-30-univention-management-console-frontend.yaml OK - Error message guidance instead of endless login screen OK - debian/changelog OK - yaml |
This can be reproduced when the UMC server process is not running. The login process appears is endless, although a 401 error is returned upon the auth command. This seems to be an error in the JavaScript handling in LoginDialog: > ... > array.forEach(forms, lang.hitch(this, function(ff) { > var form = ff[0]; > var iform = ff[1]; > this._connections.push(on(iform, 'submit', lang.hitch(this, function(evt) { > ... "iform" has the value "null" which causes an exception in the on() function. An error message should be shown instead. Maybe we could also add a hint that the server process is not running?