Registration failures due to SSL misconfiguration should be more explicit
Bug #1409700 reported by
Chris Glass
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
Wishlist
|
Chris Glass | ||
landscape-client (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Trusty |
New
|
Undecided
|
Unassigned |
Bug Description
One of the most common errors when trying Landscape LDS (seen on stackoverflow, reddit, etc...) seems to be that landscape-client requires the server certificate to be signed by a CA, unless the server's public key is specified manually.
Yet the failure message is a completely generic one (Failed to connect). It would be good if the SSL failures had a specific message so as to point the users in the right direction.
Related branches
lp://staging/~tribaal/landscape-client/more-information-on-ssl-errors
- Данило Шеган (community): Approve
- Free Ekanayaka (community): Approve
-
Diff: 291 lines (+141/-19)8 files modifiedlandscape/broker/amp.py (+2/-1)
landscape/broker/exchange.py (+13/-2)
landscape/broker/server.py (+2/-2)
landscape/broker/tests/test_amp.py (+1/-1)
landscape/broker/tests/test_exchange.py (+39/-2)
landscape/broker/tests/test_server.py (+18/-4)
landscape/configuration.py (+14/-6)
landscape/tests/test_configuration.py (+52/-1)
lp://staging/~benji/landscape-client/better-self-signed-cert-ux-3
- Björn Tillenius (community): Approve
- Chris Glass (community): Abstain
- Данило Шеган (community): Approve
-
Diff: 1345 lines (+604/-570)4 files modifiedlandscape/broker/amp.py (+15/-0)
landscape/configuration.py (+108/-90)
landscape/tests/helpers.py (+1/-0)
landscape/tests/test_configuration.py (+480/-480)
tags: | removed: kanban |
Changed in landscape-client: | |
status: | In Progress → Fix Committed |
Changed in landscape-client: | |
milestone: | none → 15.04 |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.