Univention Bugzilla – Bug 33705
UMC-Server: revise UMCP auth response when authentication fails
Last modified: 2015-11-24 11:05:52 CET
Currently these cases exists when a UMCP authentication can fail: Wrong password: {"status": "411 Length Required", "message": "The authentication has failed"} → Should be 401 LDAP down: {"status": "411 Length Required", "message": "The authentication has failed"} → Should be 503 univention-management-console-server is down: {"status": "401 Unauthorized", "message": "No permission -- see authorization schemes"} → Should be 503 univention-management-console-web-server is down: 503 Service Temporarily Unavailable → Is correct
(In reply to Florian Best from comment #0) > Currently these cases exists when a UMCP authentication can fail: > > Wrong password: > {"status": "411 Length Required", "message": "The authentication has failed"} > → Should be 401 I guess 411 is OK. > Status( 'BAD_REQUEST_AUTH_FAILED' , 411, ( 'The authentication has failed' ) ),
*** Bug 35571 has been marked as a duplicate of this bug. ***
(In reply to Alexander Kläser from comment #1) > (In reply to Florian Best from comment #0) > > Currently these cases exists when a UMCP authentication can fail: > > > > Wrong password: > > {"status": "411 Length Required", "message": "The authentication has failed"} > > → Should be 401 > > I guess 411 is OK. > > > Status( 'BAD_REQUEST_AUTH_FAILED' , 411, ( 'The authentication has failed' ) ), No it is not. A HTTP client thinks that he did not send a Content-Length request header then.
In UCS 4.1 only 401 is used with some flags which indicated the failure (password expired, ...).