Bug 1145347 - Inconsistent terminology around Login vs Sign Out
Summary: Inconsistent terminology around Login vs Sign Out
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: foreman
Version: Foreman (RHEL 6)
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: Installer
Assignee: Dominic Cleal
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On: 1145639
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-22 21:32 UTC by Matt Reid
Modified: 2015-04-30 15:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1145639 (view as bug list)
Environment:
Last Closed: 2015-04-30 15:41:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Current Login screen (421.47 KB, image/png)
2014-09-22 21:34 UTC, Matt Reid
no flags Details
Sign out menu item (39.63 KB, image/png)
2014-09-22 21:35 UTC, Matt Reid
no flags Details

Description Matt Reid 2014-09-22 21:32:49 UTC
Description of problem:
When you need to log in to RHEL OSPI, you're asked to Login, but to unauthenticate yourself, you click on Sign out. Ideally, these would use the same terminology, and either be Sign In and Sign Out, or Log In and Log Out.

We've recommended using Log In/Log Out with Patternfly.
https://www.patternfly.org/wikis/patterns/loginlogout/

Version-Release number of selected component (if applicable):
foreman-installer-1.5.0-0.6.RC2.el6ost.noarch
rhel-osp-installer-0.1.10-2.el6ost.noarch
openstack-foreman-installer-2.0.20-1.el6ost.noarch
ruby193-rubygem-staypuft-0.2.5-1.el6ost.noarch


Additional info:

Comment 1 Matt Reid 2014-09-22 21:34:39 UTC
Created attachment 940202 [details]
Current Login screen

Comment 2 Matt Reid 2014-09-22 21:35:04 UTC
Created attachment 940203 [details]
Sign out menu item

Comment 5 Mike Burns 2015-04-30 15:41:13 UTC
Upstream foreman issue.  We'll get it after they fix it in our next rebase, but we don't plan to rebase at this time.


Note You need to log in before you can comment on or make changes to this bug.