Bug 837084

Summary: Usability issue on success page when adding cart which has secured web UI link with credentials
Product: OKD Reporter: Dan Mace <dmace>
Component: WebsiteAssignee: Steve Goodwin <sgoodwin>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: mpatel, sgoodwin, yujzhang
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-13 23:43:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
new visuals for reference none

Description Dan Mace 2012-07-02 17:42:19 UTC 
Description of problem:

When adding a cartridge which provides a secured web UI (e.g. Jenkins), the resulting success page does not provide any visual contrast or other obvious cues as to the importance of noting the credentials, especially given the lack of a password reset mechanism. If the user does not make note on that single page, the cartridge UI will be rendered forever inaccessible to the user. The lack of visual contrast and cues could cause users to gloss over the page and navigate away.

Version-Release number of selected component (if applicable):


How reproducible:

Add a Jenkins server cartridge, and look at the resulting success page.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

A low-contrast success page which does not provide sufficient warning to the user of the implications of losing the listed credentials.

Expected results:

A more obvious explanation of the ramifications of losing the credentials, as well as more visual contrast to prevent the user from glossing over the success page.

Additional info:
Comment 1 Clayton Coleman 2012-07-03 02:56:31 UTC 
Multiple problems here - there should be a way of retrieving this info at anytime, and a better visual display of the attributes when they are retrieved.
Comment 2 Steve Goodwin 2012-07-09 21:28:02 UTC 
It would be beneficial if each individual app had it's own "settings" page that would contain this and other key information, so it's accessible to the user at all times.

Looking through the backlog, I couldn't find a user story pertaining to this issue.
Comment 3 Clayton Coleman 2012-07-10 01:53:37 UTC 
Steve was going to address the visuals.  Settings is further out - we will have to prioritize it eventually but it's not yet on the radar.
Comment 4 Steve Goodwin 2012-07-10 14:26:02 UTC 
<pre> code block styles modified for high contrast with surrounding text.
Comment 5 Steve Goodwin 2012-07-10 14:27:18 UTC 
Created attachment 597354 [details]
new visuals for reference
Comment 6 Yujie Zhang 2012-07-11 07:51:07 UTC 
(In reply to comment #5)
Tested this issue on devenv_1884, the new visuals for reference has been added.