Evergreen

Confusing staff client error message for unsigned SSL certificate

Bug #1056357 reported by Warren Layton
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
Evergreen 2.3.1

Bug Description

When using the staff client to connect to an Evergreen server with an unsigned SSL certificate, a warning box appears that indicates (incorrectly) that there is a version mismatch between the staff client and the server. Clicking on "Add SSL Exception" resolves the issue but the inaccurate error message doesn't lead a new user to think of this solution.

Evergreen version: master git branch from just after 2.3 release (most recent commit when I do "git log" is 4a2a2d03991ec30a2a61d71dca690b90ac84a30a)
OpenSRF: master git branch (most recent commit when I do a "git log" is 56e5f5d796bcbf80bd8e801d523fc9e2aee3947d)
PostgreSQL 9.1.5
Linux distribution: Ubuntu 12.04 (Precise)

Revision history for this message
Thomas Berezansky (tsbere) wrote :

I believe that the branch in bug 1032325 fixes this issue.

Revision history for this message
Michael Peters (mrpeters) wrote :

I agree with Warren. This is misleading. While a default hostname would be good, it doesn't account for those organizations who rely on community built clients, or people who might access test servers without SSL certs.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Low
tags: added: https ssl staffclient
Revision history for this message
Thomas Berezansky (tsbere) wrote :

Allow me to clarify:

I believe the branch in question fixes the issue in the process of adding default hostname support, without needing a default hostname set to get the benefit of solving this issue.

Revision history for this message
Ben Shum (bshum) wrote :

Tested the branch and it gives the message:

"There was an error testing this hostname." in red as the status check. Nothing about bad version, etc. Once you click into the Add SSL exception, then it begins to work.

Better than the popup message from before.

Revision history for this message
Ben Shum (bshum) wrote :

Given the massive confusion with these errors, I think we should merge tsbere's fix from bug 1032325. Even though it adds "new" features, it won't be usable until properly documented as an option during the installation process.

Changed in evergreen:
milestone: none → 2.3.1
importance: Low → Medium
Revision history for this message
Ben Shum (bshum) wrote :

Pushed tsbere's fix to rel_2_3 to fix this problem in future releases.

Changed in evergreen:
status: Confirmed → Fix Committed
Jason Stephenson (jstephenson)
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.